New Lister app Swift bug: "No matching provisioning profiles found", "App ID with id ... not available"
I downloaded the sample code for the Lister app from the Apple developer website and am trying to create a Swift version for my iPhone 5S with iOS 8 Beta 5. I changed everything to com.mycompany.Lister but when I try to create it the following error occurs.
No matching provisioning profiles found
None of the valid provisioning profiles allowed the specified rights: com.apple.developer.ubiquity-container-identifiers. Xcode can fix this problem by downloading a new provisioning profile from the Member Center.
So, I click on "Fix Issue", it loads in a few seconds and comes back to me with this message:
The app id with id 'com.example.apple-samplecode.Lister.ListerToday' is not available. Enter another string.
I thought I already changed everything for com.ycompany.Lister, but maybe I was hiding something somewhere.
source to share
Your build settings change code signing IDs from distribution to developer or not code signing.
As per @markerberg's comment: the trick is to go through the compilation settings for all 8 items (toggle through the dropdown in the top left corner of the build settings). For each of the purposes, you need to change all of the code signing parameters so as not to enter the code. Then it works right away.
source to share
I fixed this by creating an App Store Distribution Profile for my app on developer.apple.com provisioning portal. Here are the arguments. https://developer.apple.com/library/ios/qa/qa1830/_index.html
I'm sure Xcode did it automatically for me the last time I created an objective-C app, but this is my first Swift app and I think I had to do it manually even if I was just submitting beta testing via TestFlight.
source to share
I followed the instructions in the ReadMe file that came with the source code (called iOS and Quick Start). But when using Xcode's "Fix Issue" option to generate Provisioning Profiles, I got the error mentioned above.
I had to go away and restart Xcode to fix this issue. After restarting Xcode, the Fix Issue function seemed to work for me.
source to share