I now have an iPhone 5 that I want to use for development. I try to add provisioning profiles in Organizer but they are greyed out. Can't the same provisioning profile be used on multiple devices?
When I have Provisioning Profiles selected in Organizer for the new device, I click on the + symbol on the bottom left to add a provisioning profile. I navigate to the correct location of the profile and as I mention above, they are greyed out. There is no way to add it this way.
Linda
In Xcode organizer after selecting the device you able to find an option "Add to Portal".Then sign in with your valid apple developer account.Then Everything will be configured automatically.
Linda, the same provisioning profile can be used on multiple devices.
In your case, the chances of the provisioning profile being greyed out may be because:
The device which you are using is not registered under the provisioning profile you are trying.
Provisioning profile binds
Certificate
App ID
UDID of the device.
All the above 4 bind and work together.
provisioning profile can use to multiple device.
Your case because in your provisioning profile not included your iPhone 5 (UDID).
Please check in https://developer.apple.com/
add your UDID
Create New Provisioning Profile
Add your Provisioning Profile To XCode
Check in Organizer
Related
I am working on one side project, it has image view where a user can click and select an image from the photo library. I am using UIImagePickerController.
My question is I haven't added user Permission on plist nor anywhere else. and as far I know app crashed if you don't add permission, Plus when the app opens for the first time the dialog appears asking for permission but in my case, it's not asking.
I like to know how this can be possible or does Apple have changed something in new Xcode or OS?
I am using Version 9.2 (9C40b) and tried running the code on iPhone 6(real device iOS 11.2.6,) and in different simulator same result, I deleted the app and run it again, same no dialog.
And if Apple has changed something in iOS 11, Should we add or not the permission? whats the best way to a developer we don't want to ask, and also don't want the app to be crashed.
The answer is YES you have to provide the description
It is mandatory to add usage description(from iOS 11) of permissions you are going to use.
Apple states that
Your app is responsible for all usage of privacy-sensitive data, including access to this data by all third-party libraries used in your app. If your app attempts to access privacy-sensitive data without a usage description, your app will exit.
You will see this error in console log if permission description is not provided in Info.plist
This app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCameraUsageDescription key with a string value explaining to the user how the app uses this data.
If you try to submit the app without description for release Apple will reject it with this message
Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSSpeechRecognitionUsageDescription key with a string value explaining to the user how the app uses this data.
Summary:
If you have not provided usage description and uploaded the app earlier then your app will crash without asking for permission
If you have not provided usage description and tried to submit recently then apple will reject it.
Reference:
Privacy Settings in iOS 10
Xcode archives successfully using the latest - and correct - provisioning profile.
However, the Bots configured in Xcode Server still use an older profile.
This can be seen if one authenticates as xcodeserver user and navigates to ~/Library/MobileDevice/Provisioning Profiles.
Running security cms -D -i myuuid.mobileprovision confirms this.
Having tried reconfiguring a new Bot, restarting Xcode Server, deleting the old profile, and so on, nothing works.
How can we help Xcode 9 Server do what it promised, and use the latest provisioning profile from the Apple Provisioning Portal?
A dirty hack will work. This is assuming Xcode will correctly Archive using the correct profile. Unarchived the resulting .app file, then rename the embedded.mobileprovision file according to it's UUID, e.g.
myuuid.mobileprovision
Next, copy myuuid.mobileprovision to the ~/Library/MobileDevice/Provisioning Profiles folder.
Identify any older profiles linked to the same bundle identifier and delete. To play it safe, consider moving temporarily to ~/Desktop.
Finally, integrate the Bot, unarchive the resulting .app., and inspect to confirm creation expiry date, UUID, and UDID array are all as expected:
security cms -D -i embedded.mobileprovision
After upgrading from Xcode 7.3 to Xcode 8, I'm getting an error:
Provisioning profile "iOS Team Provisioning Profile: *" doesn't
support the Wireless Accessory Configuration capability.
May I know how to resolve this?
You should enable it in apple's developer portal.
Go to "App IDs" and edit your app.
Check the Wireless Accessory Configuration checkbox.
Cick Done
Now just regenerate your provisioning profile and rebuild/archive using newly generated profile.
1 apply for rights ： https://developer.apple.com/contact/network-extension/
2 check the Wireless Accessory Configuration checkbox in Xcode
3 selected Wireless Accessory Configuration when create Provisioning Profile
Go to the Target -> General -> Signing
Click on Automatically Manage Signing and choose a team Account.
press command+,
enter Accounts
re Download All Profiles.
I had an app created for me--Demeter's Harvest (iOS). The company that built it has dropped off the map, so I can't get them to help me with this.
I get a message when I try to access it all that reads: An App ID with Identifier 'info.NAMEOFDEVELOPER.demeter' is not available. Please enter a different string." and another one for the Bundle ID that shows the Identifier 'info.ORIGINALDEVNAME.demeter' with the version and build.
I placed my name into the team area, and got a message that says no non-expired provisioning profiles are installed with a "Fix Issue" button.
How do I go about gaining access to my app code (if that is what it does) so I can get a new developer to make changes and updates to it?
Thanks,
Ed
You're likely up a creek here. If you don't have your app code there's no way anyone can help you gain access to it except the developer.
Regarding the bundleID it will be tied to whichever Dev Portal created it. If you own that portal you're fine. If the developer owns that portal and they either don't renew their account or block you from accessing it there will be no way for you to re-use it.
I haven't really used the archive function under Xcode 3, but got used to it now in Xcode 4. So far I always used to have three or four build settings in all my projects: Debug, Distribution AdHoc and Distribution AppStore. Distr. AdHoc and AppStore were both copies of "Release" and only differed in regard to their provisioning profile selected for Codesigning (so essentially they were a thing of convenience, making sure I never sent the wrong person the wrongly signed build).
Now I noticed that Xcode asks me with which profile I would like to sign my build with whenever I export an archived build form the organizer, yet at the same time the build would also fail if the selected provisioning profile in the build settings was not valid. Are Xcode 4 archives provisioning profile independent from or are thy tied to a provisioning profile? How do you solve the "challenge" of having to build for AdHoc and AppStore without having too many build settings groups (switching the groups associated with the build schemes has become somewhat cumbersome in Xcode 4)?
Thanks!
in Xcode 4 if you archive an application it is signed with the provision profile that you have indicated to use under its build configuration. Most likely a settings that was carried over from an Xcode 3 project.
An archived app can be resigned with a different provision profile at a later time (though the organizer or command line), so in a way, yes they are independent of provision profile.
Two suggestions for managing building for AdHoc and AppStore:
1)
The first is taking advantage of Xcode 4 schemes, and creating a new schemes for AdHoc and AppStore
Under the Schemes Menu: Edit Scheme -> Duplicate Scheme, then under the Archive you can select your desired build configuration (AdHoc, AppStore, etc...), you can then name this scheme AdHoc, AppStore to match too. When you want to build for release just select the target scheme and it will sign it with the associated provision profile from the build configuration.
2)
Maintain 1 scheme, remove code signing from your build configurations, and code sign apps exclusively though the organizer after archiving.