Xcode errors when uploading iOS 7 app via Organizer, every time - iphone

Xcode is giving me 3 errors whenever I try to submit my iOS7 app through Xcode. The errors are:
Apple's web service operation was not successful
Unable to authenticate package
The bundle 'com.x.x' at bundle path 'Payload/x.app' is not signed using an Apple submission certificate. at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)

Change "Valid Architectures" in Build Settings to "$(ARCHS_STANDARD)". After banging my head on this for almost 2 days, and thinking I had tried the architectures fix, I realized that I had only tried changing the "Architectures" to standard (which kept giving me an error on build), and not the "Valid Architectures".

Related

Code-signed IPA runs on iOS7 but not on iOS8

I have a version of an app that runs on iOS8 and iOS7 and I want to codesign it for Enterprise deployment. When I do this, it runs successfully on iOS7 but on iOS8 when tapping on the app it hangs on installing with just a grey icon.
One thing I've noticed is that the latest unzipped Payload from the vendor does not include a ResourceRules.plist file, wondering if that may be the issue?
I've tried code signing without a ResourceRules.plist, using an old (possibly inaccurate?) ResourceRules.plist, and using a different provisioning profile and certificate. Got the same behavior as above every time.
What else should I check to try to resolve this? Thanks
EDIT: I'm getting the following in debug while doing the install (identifier/app names changed to aaa, bbb and ccc for privacy reason):
Jan 14 11:06:09 Brads-AIR atc[31] : 0x101f7c000 __MobileInstallationInstallForLaunchServices_block_invoke240: Returned error Error Domain=MIInstallerErrorDomain Code=37 "Appex bundle at "/private/var/mobile/Library/Caches/com.apple.mobile.installd.staging/temp.FYHYX8/extracted/Payload/CCC.app/PlugIns/Photo.appex" with identifier "com.aaa.AAA" does not have expected identifier prefix "com.bbb.BBB"" UserInfo=0x12ff52da0
OK I figured this out. Problem was that the plug-in nested within the app bundle also needed code-signing first (remove its _CodeSignature, change bundle identifier in its Info.plist, replace its embedded.mobileprovison, codesign it separately), just as though it were an app within an app that needed configuring first.

Another 'no identities are available for signing' issue

So i'm attempting to submit my app to the app store and getting the 'no identities are available for signing' error.
Ive gone through and remade my distribution certificate about 5 times so far in the provisioning portal, re-downloaded it (through xcode) each time and to no avail it still gives me the error.
Ive adjusted the code signing in the build settings to be set to the 'iPhone Distribution: (my certificate name)' as well as making sure my bundle identifiers match.
Ive restarted XCode multiple times and nothing seems to be working.
ideas?
Have you tried cleaning your project? This oftentimes resolves such issues with my own projects.
Product ==> Clean

Cannot get passed the Validation stage of submitting app with iPhone 5 support

This is an old app that's been submitted many times without problems. I've modified the code and the info.plist to support iOS 6 and iPhone 5, but didn't change the build settings at all. I've checked the certificates and provisioning profiles, they are all sound. All adhoc builds ran just fine on our devices. I'm using Xcode 4.5.
I build without errors and it archives just fine. It shows up in the Organizer. When I click Validate..., I click through just like normal, pick the right provisioning profile, but then it fails every time with the same three errors:
Unable to run the lipo command /Applications/Xcode.app...: can't open input file: ...(No such file or directory)
Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate.
The binary being analyzed must exist: ...
I've tried the answers in the following question: Binary being analyzed must exist, iOS App Archive in xcode and my app checks out.
I suspect the problem is that I've included armv6, armv7 and armv7s as valid architectures, but I really have no idea what the problem is because this all worked in Xcode 4.4.
What do I do to fix this?
You can not build armv6 binaries using Xcode 4.5, the support for armv6 has been dropped by Apple.
It seems your errors are pretty much compounded after it reaches the first error so if you fix it so it builds for armv7 and armv7s then it should fix the rest of the errors (since it'll generate a valid binary if the script is fine with everything else and be able to be analysed)

iOS codesign error

I continuously get the following warning when I build my iPhone application:
Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)
But my application still runs. Why is this occurring? Can someone help? I updated my application and the App Store approved it, but now it crashes everytime anyone runs it (after installing the update) and I have no idea why. And now, I can't even get this warning to go away.
Here's my todo list when I've run across this.
1) Clean all targets, exit Xcode, then go drag the build folder from your project to the trash.
2) Do the Get Info on your project, make sure the Code Signing Entitlements and Code Signing Identity are selected correctly. Do the same for your Targets.
3) Login to the iOS Provisioning Portal and make sure the Distribution certificate has not expired. Also check the Distribution Provisioning Profile and make sure it is Active. Make sure the Certificate is properly in your Keychain and the Distribution profile is in Xcode Organizer (if you have multiple of the same one, delete all but the correct one and redo step #2).
4) Look at your Build Results on the failure and identify which profile it is actually using and make sure it is the right one.
It seems that this is a bug in Xcode, I have read somewhere people reporting that warning after upgrading it. I have the same problem, I can compile and run the App, I have already released the App to the AppStore, but I just can't get rid of that annoying warning.
I think you can have a try to reset Keychain, before I encounter a problem that show my certificate was expired or invalid and I can not run with mobile, then I reset Keychain, then it worked well.

Dreaded "The executable was signed with invalid entitlements"

i have the "The executable was signed with invalid entitlements" error. The error only occurs when im trying to set TRUE to the Entitlements.plist of get-task-allow. The reason for trying to do this is because im trying to get the device token to be shown in the console, using the device token later for push notifications.
Though, if i set false to get-task-allow, the app would build in the iPad.
Currently using XCode SDK 3.2.3, iPad iOS 3.2.1
I Have tried everything from removing all the keys,certificates from the Mac. Revoking the certificates in the iPhone Provisioning Portal. Removing the provisioning profiles in the iPad. Then redoing everything all over again.
I also have checked in the Project "Application" Info that under the Code Signing Identity , it is set to iPhone Distribution : "Name".
Also have checked in the Target "Application" Info for the same thing. Then done a clean build and run but still having this error.
The simulator cannot get you a device token, (just in case you didn't know).
On the device, if you have jailbroken it, I am not able to get a token. You need to have an untainted phone.
The error you are getting is because you a selecting the wrong certificate.
Follow these instructions carefully
http://blog.boxedice.com/2009/07/10/how-to-build-an-apple-push-notification-provider-server-tutorial/
Your certificate could also have expired for push notifications, check that as well.
i solved it, The organiser window of XCode > Window > Organiser . In the Devices tab, when you click on a device that is connected, there is a console pane on the right. you can then use that to find out your device token if "get-task-allow" is not allowed.