I had a developer account (without payment) to try some thing with iOS apps (with Unreal).
Now I erased my old Macbook because I got a new Macbook.
Now I installed Xcode again and wanted to get access to my iOS Development certificates but I can't do anything with them because they are greyed out.
I am stuck and don't know how to "reset" the old certificates now.
Is the info I require on my old Macbook and therefore gone forever and I will need to create a new account?
What can I do?
Thanks for any help in advance, Chris
Chris:
>I had a developer account (without payment)
That means you didn't have a _developer_ account...you simply had an Apple ID tied to an Xcode 'free provisioning' account. You can't follow processes related to a paid Developer Program account if you don't actually have one, so don't be confused by that.
Open Keychain Access and remove any expired/duplicate certificates, then delete all accounts from Xcode Preferences/Accounts. Then quit and re-run Xcode. Using the same Apple ID, re-add an account to Xcode for use w/free provisioning. See details below that are specific to that process.
Free provisioning/testing/tinkering on your device:
• From within Xcode 8.x or higher (Mac only), navigate to “Xcode—->Preferences—->Accounts.” Hit the '+' icon below left to add your Apple ID*. After you add and select your account, it will show within the main account window on the right under ’Team' as ‘<YourName> (Personal Team)’ w/role ‘User’.
• Connect your device (cable only, not wireless) and select it as build destination via the 'active scheme' dropdown to the right of the play and stop icons.
• In target's 'General' tab/settings:
• a. Set app identifier/bundle ID you want for your free profile - note this must be unique, meaning if it is already in use, you can expect an alert warning is it is already in use and you should enter a different string. If you expect to make this app for store distribution later, you will either need to change again, then, or make a plan now that includes a naming scheme.
• b. Set team id as 'Personal Team' ...the apple id used w/free provisioning
• c. If you see provisioning profile warning at this point, use 'Fix Issue' button directly below
- You may have to ‘Fix Issue' more than once - keep at it so Xcode can step thru them as needed.
• Run your app with your device selected.**
Free provisioning secrets/things you’ll want to know:
- The profile will be valid for 1 week, after which time you will need to recreate a new one (delete the account from Xcode and repeat the process).
- There is a limit to how many apps you can build and test to your device. If you hit this error, delete old versions and try again.
- Maximum number of (connected only) devices limit is reported as 3. And unlike a paid Developer Program account, there is no Member Center/devices access/management.
- What you can/can't do w/free provisioning is listed here:
https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/SupportedCapabilities/SupportedCapabilities.html#//apple_ref/doc/uid/TP40012582-CH38-SW1 - In App Purchase, as an example, is one of the features not avaliable w/free provisioning.
- If you see an error that says "change your Bundle Identifier to a unique one”, that means don’t use the same string (and/or the string is malformed; no special characters, hyphens, underscores, spaces etc.) such as: com.sample.app …add your last name or some string to the end such as com.sample.lastname, then click on ’Try Again’. Note: You may need to change it again if your app goes to the store. Don’t use a string here that you intend to be in the store later. Use something non—important. If you make this change, follow it up by using the ‘Product’ menu while holding down on the option key, then choosing to ‘clean build folder’.
- If this is about creating an .ipa to manually hand off, select Build For Archiving under the project menu, not ‘Run’.
- *If you have, had or plan to have, a paid Developer Program account, be sure to use a unique/different apple ID for each account.
- **Free accounts may experience issues launching apps on the watch for the first time.
Workaround: Launch the app manually on the device and click “Trust” when the security sheet appears. You should then be able to launch the app from Xcode.
Ken