I have searched for the solutions but none worked for me. I have uploaded the build so many times, it also shows processing in the activity tab but after finishing upload from Xcode, it just vanished. On clicking the Add button under the Build Option on iTunes Connect, it shows me the old build, the rejected one.
I also have the NSCameraUsageDescription and NSPhotoLibraryUsageDescription strings in Info.plist.
What could be the problem? Any help?
If you see your build under My Apps/TestFlight/Builds/iOS with a Missing Compilance warning, you should click on the yellow triangle and on Provide Export Compliance Information afterwards.
After you provided the necessary information, your version will be selectable.
Related
With Xcode 10.2 I'm getting a Code Signing failure of
resource fork, Finder information, or similar detritus not allowed
Command CodeSign failed with a nonzero exit code
but I don't how to find which particular element of the massive project is causing the problem.
This, by the way, was not occurring with Xcode 10.1. Back then I did find that some of my .png images contained color profiles which were removed and stopped a code signing failure there.
The current failure occurred after bringing the code unchanged from under 10.1 where no failure happens. And it does not happen either when I take the code as modified under 10.2 back to 10.1. So this is making me crazy!
Now, I can't even find Apple documentation to help me find what to fix! Any suggestions will be gratefully processed. Thanks.
I examined (again) the dense paragraph above the code signing error message. The main thing it contained was a path to my app bundle. So I thought something extraneous might be within the bundle.
I went to the Products folder in the project navigator panel in Xcode and right-clicked my app, then selected Show in Finder, then in the Finder I right-clicked the app and selected Show Package Contents, then expanded the Contents directory and then the Resources directory which is the most likely place to find detritus.
Sure enough, there was a .png image file which I had rejected for use while experimenting with the app. I had commented out // the code lines referring to it, but had not deleted that image file from among the Supporting Files in the Xcode navigation panel.
I did delete it and re-built the app. Voila, no more code signing fault!
Thanks, guys, for your kind attention to this question, and all the questions people ask.
I am trying to submit my app to the App Store however I am having issues with Provisioning Profiles.
When I click Submit after having archived the app, I receive the error:
No matching provisional profiles found - None of the valid provisioning profiles allowed the specific entitlements: applications-identifier, beta-reports-active, keychain-access-groups.
Here is my settings (I have the both the same settings in build settings in both the project and the target):
How can I fix this?
I was able to fix this problem by changing the Architectures setting. I assume this was just a problem with Architectures/Valid Architectures being incompatible with one another.
For me, the issue was that a tool I was using for image resize got into the images resources that the app was bundling up. So, whilst it happily build and archived all the .png's and this rogue .app the app store barfed on it.
In the end, looking at the console log gave me the clue I needed. As soon as that file was taken out the warnings about applications-identifier, beta-reports-active and keychain-access-groups.
I know this has been asked and answered multiple times but I'm tearing my hair out as none of the proposed solutions appears to work.
I receive the above error, despite having a valid provisioning profile which, as far as I can tell matches the bundle identifier:
I've followed the steps in various suggested solutions on this site, including deleting all existing certificates and starting again, as suggested here and here.
One thing I have noticed is that the profile doesn't show up in the code signing lists, either for target or project.
Can anyone offer any further suggestions?
This happened to me yesterday. What happened was that when I added the device Xcode included it in the wrong profile by default. This is easier to fix now that Apple has updated the provisioning portal:
Log in to developer.apple.com/ios and click Certificates, Identifiers & Profiles
Click devices and make sure that the device in question is listed
Click provisioning profiles > All and select the one you want to use
Click the edit button
You will see another devices list which also has a label which will probably say "3 of 4 devices selected" or something of that nature.
Check the select all box or scroll through the list and check the device. If your device was unchecked, this is your problem.
Click "Generate"
DON'T hit Download & Install – while this will work it's likely to screw up your project file if you've already installed the provisioning profile (see this question for more info).
Open Xcode, open the Organizer, switch to the Devices tab, and hit the Refresh button in the lower right corner. This will pull in the changes to the provisioning profile.
Now it should work.
If none of above stated works then check for your device date, make sure your device date doesn't exceed profile expiry date i.e. not set to far future.
+1 to banging my head against the wall for a day or two...
Also check this setting:
Build Settings -> Code Signing -> Provisioning Profile
After following the above steps, "Automatic" setting worked for me. ~kjm~
File > Workspace Settings > Set Build system to "Legacy Build System"
Xcode5 has broken this again (congratulations to Apple for failing to bother testing one of their buggiest bits of code. Again).
A new way to break/fix it:
If you have:
An old profile on your device (team profile, or non-team profile)
A new profile generated automatically on the App Store, by any copy of Xcode5, even if it's simply an update to the profile you already had
(NB: if any colleague adds themself to the profile, this triggers the above "change")
You use the new "Accounts" dialog to download profiles (NB: this is now REQUIRED by Apple for various situations - all other approaches, including manual download, appear to be unsupported. Even though the Apple Developer site TELLS YOU TO MANUALLY DOWNLOAD! Don't do it! It breaks Xcode5!)
Xcode5 will INCORRECTLY hide AND RENAME that profile in the drop-down selector in Build Settings
(I detest this drop-down. Some idiot at Apple keeps removing information from it, and someone else keeps adding it back, it flip-flops between Xcode point releases. WHY??!?!)
There is NO WAY you can select the correct profile - whatever you select, Xcode5 will use the wrong one
The solution is easy enough. The "Apple engineering are lazy" solution:
Go to Xcode5 -> Window -> Organizer -> Devices
Select your device
Select provisioning profiles
Delete everything relating to your current project and/or Team (even other projects, if necessary - they can all be downloaded later if still needed!)
Re-build.
You should get an error from Xcode5 that the profile doesn't exist. Even though you manually had seleted the profile that was ALREADY PRESENT on your machine (yep - that dropdown is buggy again. It lies about the profile it selects behind the scenes!)
In the profile selector, select the "real" profile
Build, run - success!
It happened to me when I accidentally left the build in release mode.
This can happen if your provisioning profile has expired. Another reason could be that you device date exceeds the expiry date of your provisioning profile. Please make sure that your device date is correct.
After spending the day I realized it was a simple change in Project Settings
File -> Project Settings... -> Build System -> Legacy Build System.
In a project setting, you will see Build System named drop down and in that drop down select Legacy Build System
Delete all certificates from the keychain of the account which you are trying to use provisioning profile
Delete Derived data
Clean the folder(cmd+sht+alt+k)
Clean the project(cmd+sht+k)
Build & Run
In my case it was just after a new Program Licence Agreement was released so we had to accept them and it was fine.
I had this error because I was testing my app to perform a certain action in the future. In other words, I had a different time on my test device, therefore, the certificate would not allow me to build.
Apparently, my certificate expires in a few days...
In my case, it was the problem when I setup my time manually two month earlier on my iPhone. But when I changed to set time automatically, it worked fine.
Setting -> General -> Date & Time -> set time automatically
If it does not work then set time automatically of both mac & iPhone, it may work fine.
I have spent about a week solving this problem. Most of the answers are sort of magic (no logical purposes for these algorithms) and they were not useful for me. I found this error in Xcode console:
ERROR ITMS-90174: "Missing Provisioning Profile - iOS Apps must contain a provisioning profile in a file named embedded.mobileprovision."
And found this answer solving this issue. The case is to switch Xcode Build system to the Legacy one.
I was deploying my Ionic app.
After wasting my half day I got this working.
Select Target > Edit Scheme > Select Run > Change Build Configuration to debug
I'm still not sure what the issue was but deleting all certificates and starting over (albeit twice) eventually solved it.
My best guess is that I've missed some small but important detail of the procedure. Unfortunately I can't be any more specific than that.
Make sure you have added your device - https://developer.apple.com/account/ios/device/create
Go into iTunes and click on the serial number and it'll change to the UDID - then right click to Copy the UDID and register it as your device.
You can then add that device to your provisioning profile.
I installed Xcode 4, thinking it would be similar to Xcode 3, and now I cannot get my binary to the App Store using organizer which I believe is the proper way to do this.
Has anyone got this working properly? Not sure what setting I need to update - All I get is an "invalid binary" message. Of course, it is a critical update I need to submit.
I've had something similar. You should check your code signing settings. Xcode 4 introduces "schemes", which are a little complicated. Think of them as sets of configurations. In Xcode 3, you could only have one such set of settings.
I believe that you need to check your code signing settings for your active scheme. Check the "Archive" option.
Edit your code signing settings:
Then, ensure that your "Archive" option is using the correct signing settings. Click on the "Edit Scheme" entry in the menu on the top left of your window.
And then verify that the proper signing setting is being used:
Depending on how you've set up your code signing and Build Settings, you may need to adjust your schemes appropriately.
After trying a wide variety of options over a period of two intensive and enormously frustrating days, only to be faced with the cryptic and utterly unhelpful "invalid binary" message, I reviewed this post again.
When I reviewed avaynshtok's question - "You mean when you submit the binary, you have to select the distribution profile. However in the Code Signing section of the build settings, you still want the developer profile selected for the release build configuration, correct?"
Although it wasn't answered, it got me to think about the profile you select when you are in Organizer and select the "Submit" button. I took another look and realized that you need to set the distribution profile there, for which I had been just accepting the default until now.
So, I set my "AppStore" archiving profile back to use the development certificates, as suggested above. I then resubmitted using the distribution profile at the Organizer "submit" time, and voila - it passed.
Question to Apple: you guys have $70,000,000,000 in cash. Can you afford to update the apps store submission procedure docs and "invalid binary" message to be a tad more clear? I'd be fired if I produced such low quality work.
Before I upgraded Xcode and the iOS SDk to 3.2.5 and 4.2 respectively I could select text in Xcode, right click and and select find text in documentation, and it would go to the corresponding place in the documentation, however now if I do that it asks me to sign in with my apple ID, and then it tells me I'm not authorized? However I can access the documentation in a normal web browser like chrome, it's just irritating to not have the convenience of selecting and right clicking. (NB I'm not a paying developer, but I never have been)
Why is this? Is it only me? and how do I fix it?
Here's a hacky but working fix, inspired by http://www.iphonedevsdk.com/forum/iphone-sdk-tools-utilities/66298-unable-access-sdk-documentation-since-upgrade.html:
Open the file /Developer/Platforms/iPhoneOS.platform/Developer/Documentation/DocSets/com.apple.adc.documentation.AppleiOS4_2.iOSLibrary.docset/Contents/Info.plist
Change the DocSetFallbackURL value from https://developer.apple.com/library/ios/prerelease to http://developer.apple.com/library/ios/.
Relaunch Xcode, and voilà.
If you open the URL from DocSetFeedURL (in the same Info.plist) in Safari, you can download a .xar file of the documentation. Not sure what that file is, but I'm currently downloading it...
I'm a dev, also, but am blocked from accessing online documentation with "index.html is locked. Do you want to unlock it?" Type and it states that the file cannot be unlocked and suggests saving a local copy.
Here's what I see in the .plist file:
https://developer.apple.com/library/etc/redirect/xcode/ios/606
So, in short, access through Safari (inconvenient while working in Xcode-- contextual access not available-- or just download the files as suggested above.
If you're not a paying member of the iOS SDK program, then you can't access the online documentation via Xcode. Since you have the SDK, I would assume you are, so you may just be stumbling over a bug. In any case, you should open up Xcode Preferences and navigate to the Documentation tab (on the far right). By opening up this tab, Xcode will shortly attempt to download the full docsets that you are missing. You can tell this is happening because the right side of the rows will switch to saying "Getting...". You can also open the Activity window (in the Window menu) to see the progress of the download/install.