I am writing a static library and when i go to add it into my .ipa file and do an export/submit to apple i get this error.
ERROR ITMS-90166: "Missing Code Signing Entitlements. No entitlements found in bundle 'com.xxxxx.xxxxxxResources' for executable 'Payload/xxxxxxx.app/xxxxReaderResources.bundle/xxxxReaderResources'.""
I have seen a lot of post on entitlements and provisioning files on here but none dealing with static libraries. And the ones I saw didn't really help. The issue is that the resource bundle needs to have entitlements i guess.. i have tired resigning it with iResign and adding an entitlement.plist all failed.
The answer to my problem turns out that i had an executable in my resource bundle. By deleting the Compile Source Phase and the Link Binary with Libraries Phase from my Resource target this removed any executables from my resource bundle and fixed my missing entitlement error
I had to remove the CFBundleExecutable key from the Info.plist of the resource bundle. Once I did this I was able to upload to iTunes Connect without getting ERROR ITMS-90166
I had the same problem as you, thanks for your help.
I make a bundle to import my database, I've already publish a version of my app with that problem but I can't update it.
I solve the problem as you, in the xproj settings. I remove Compile Sources (where there were my database in old version) and Link Binary With Librairies (empty in old version).
My xproj look at that now, there are only two blocks:
Thanks!!!
I had this issue. Got it resolved by removing executable file in package content.
Below are steps for the same :
When you've archived your project it opens in Organiser window.
Right click on Archive and select show in finder.
Then again right click and select show package content.
This will show you entire package content such as dSYM, Product, SCMBlueprint, Info.plist etc.
Select Products -> Application -> [Project].app
Right click on this app file and select show package content
and delete it.
This will show you files such as storyboard, Info.plist, app icon etc.
Search for any executable file (with an icon of command prompt).
Select this file and right click -> move to thrash
Now, when you again upload your app it should work correctly!
Related
I have done a TON of research and done several things to try and get rid of this error. Absolutely nothing works. =(
When I go to upload my archive to the app store from within Xcode, I get the following error:
ERROR ITMS-90171: "Invalid Bundle Structure - The binary file '.app/constants.o' is not permitted. Your app can’t contain standalone executables or libraries, other than the CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure."
I have looked at several StackOverflow pages that reference this error. None of them resolve the error.
I can't even find "constants.o" in my file directory structure (in Xcode) or via command line.
For my Copy Build Resources, I only have the following:
font file (file.ttf)
Image Assets file
Main.Storyboard file
So, this is not the problem.
The only entitlement I have enabled in Capabilities is Push Notifications.
I'm pretty certain the issue is the "constants.o" that shows up on the first page when I go through the upload archive process. But, I do not know where it's coming from. Does anyone know where this file is coming from? How do I get rid of it??
In my case an implementation file was in the Copy Bundle Sources section of the Build Phases. I know OP did not have that issue but this helped me.
I had the provisioning profile set to Automatic for Xcode to determine the correct profile to use. This was the issue. Xcode was not picking the correct profile
The provisioning profile wasn't setting correctly when it was set to Automatic. I had to specifically set this in the Build Settings instead.
Constants.o should not show up in the archive process. Check your provisioning profile and make sure it is set correctly for Release Version.
I have the error: "ERROR ITMS-90029: "Storyboard file 'Main_iPad~ipad.storyboardc' was not found. Please ensure the specified file is included in the bundle with any required device modifiers appended to the filename.", When I try to submit to the app store from xcode.
I've tried all solutions that I found posted in stackoverflow with no luck.
I've removed the value for the key Main storyboard file base name in the project's info.plist file. and also I've delete the entry since it's no design for ipad, but it did not work.
I generated the IPA file and try to submit with aplication loader but produces the same error.
I was having the same issue and I resolved it by doing this:
Remove Main_iPad~ipad.storyboardc from info.plist (you already did this)
Remove your Apple ID in account Xcode->Preferences->Accounts
Close and reopen Xcode.
Add your Apple ID again (If you were using a #me account, change it for #icloud).
Clean, build, archive.
Upload to iTunes from Xcode or export the IPA and then use Application loader. In my case it worked unchecking the bottom left corner option ¨send bit code".
Im trying to submit a version of my app and after building im seeing the following screen
My app has a valid provisioning profile except one .o file that is for some reason not included in it..
That has been the case for a while now, and i have managed to submit the app without it being a problem.
A couple of day ago, after submiting a new version, i recived an email from apple saying :
We have discovered one or more issues with your recent delivery for "xxx". To process your delivery, the following issues must be corrected:
Invalid Signature - Code object is not signed at all. The binary at path [xxx.app/FooterCoverflowCollectionViewLayout.o] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html
Once these issues have been corrected, you can then redeliver the >corrected binary.
Regards,
The App Store team
I've tried the steps they recommended with no luck. Can anyone have any idea how to solve the issue ?
Removing the mentioned file, building, re-adding it to the project and building again solved the problem.
I experienced this exact problem, and would like to share what happened.
The .m file for one of the classes we had written (ie: not a third party library) had been erroneously added to the project in the "Copy Bundle Resources" section in "Build Phases". There is no reason for the file to have been there, and had been there for quite a long time.
The error described in the original post just started showing up in our latest submission to the app store last week, and from what I gather from other posts around the internet, Apple has recently changed something about their code signing and submission process. The .m was absolutely in the Copy Bundle Resources section in our last several submissions.
Simply removing this file, rebuilding, and resubmitting solved the problem. Since the file didn't need to be there in the first place, there was no need to add it back again.
There may be other causes for this error, but if you get this error, check your "Copy Bundle Resources" section the files that are being listed with zero entitlements.
I am attempting to submit a new version of my app to the App Store.
I am using Xcode 6 GM. The previous version of this app was submitted with Xcode 5.1 without issue.
After I generate the app archive, I click "Validate..." in the organiser. Xcode takes me through the process of selecting my developer team and verifies the provisioning profile that will be used.
It then starts to generate the package before failing with the message
ditto: Couldn't read PKZip Signature
Unable to extract archive. Please make sure /var/....path to .pkg is a valid zip or ipa archive.
I have navigated to the directory and tried zip on the command line - this gives an error. If I rename the file to .zip then Finder is happy to unzip it, but Zipeg also returns an error.
What I have tried:
Build->Clean
Recreated the provisioning profile
Recreated my signing certificate
Checked all of the "code signing" settings are the same as for my other projects that work
I have also looked into the log files that are created by the packaging process and there is nothing untoward listed until the error about the invalid zip file.
Has anyone seen this?
I have received details of a work-around from Apple developer support.
Open your target's Info.plist
Select an entry in the plist and then select "Show raw keys & values" from the Editor menu
Ensure the key "LSRequiresIPhoneOS" has the value "YES" (add it if necessary)
Regenerate your archive and submit
I'm getting an error when trying to do an archive build for ad hoc distribution on iOS for an iPhone-only app. The app is signed with the proper certificates and has the proper provisioning profile (checked with a friend who was able to sign properly as well, so it's not a code signing issue).
Whenever I try to distribute with the Xcode archive panel, I get the following error message in an alert sheet:
OSStatus error -67028
I've never encountered this error before. I'm able to build and have the app run fine in both the simulator and device, but for whatever reason, I'm completely unable to get the distribution feature of Xcode to work to create an ad hoc build.
Has anyone ran into this issue before?
Things I've checked are:
Code signing (generated all new certs and profiles to start from scratch)
Files and frameworks
The only thing that I could find with the files and frameworks that might be off is that the main Storyboard file (Main_iPhone.storyboard) couldn't be found in the Copy Bundle Resources, although the storyboard loads properly in Xcode and allows editing, and can be found in the Finder under the Base.lproj folder.
I had the same issue with the HockeyApp SDK. What I actually did was
Remove HockeyApp SDK by selecting "Remove reference" from the Frameworks folder.
Drag&Drop the Folder HockeySDK.embeddedframework to the XCode Frameworks folder
Deselect the "Copy items into destination group's folder (if needed)"
Select "Create groups for any added folders"
Select your target
According to the docs, 67028 means "The bundle format is unrecognized, invalid, or unsuitable". That is pretty vague, so I would investigate the current lead you have, that is, ensure that the Main_iPhone.storyboard file is indeed in the compiled bundle. If not, check your "copy files" build phase to ensure it is there.