Invalid binary apple store

Invalid Binary Itunes Connect [duplicate]

Im ripping my hair out over this.

I have tried like everything and evertime i submit my app to itunes connect it allways says:

(2 minutes Later)

Its Driving me mad and i have already:

Cleaned all builds

Made a new Entitlement.plist

Checked that it built with The Distribution Profile.

5 Answers 5

check up your mailbox associated with your apple developer account, apple will send email to your mailbox with some diagnose information and how to solve your problem.

for me, apple send following diagnose information. I actually have never touched iCound, which is really confusing. after all, I created a new app id without Wild-card character, then a new distribution profile, and sign my app, finally summit to apple, which turn out to be successful.

Invalid Code Signing Entitlements — The signature for your app bundle contains entitlement values that are not supported. For the com.apple.developer.ubiquity-container-identifiers entitlement, the first value in the array must consist of the prefix provided by Apple in the provisioning profile followed by a bundle identifier suffix. The bundle identifier must match the bundle identifier for one of your apps or another app that you are permitted to use as the iCloud container identifier.

Specifically, value «K8FN29QYP2.*» for key «com.apple.developer.ubiquity-container-identifiers» in ProductName is not supported.

Invalid Code Signing Entitlements — The signature for your app bundle contains entitlement values that are not supported.

Specifically, value «K8FN29QYP2.*» for key «com.apple.developer.ubiquity-kvstore-identifier» in ProductName is not supported.

I have also faced this kind of Problem and I have got this kind of Response from Apple store .

We have discovered one or more issues with your recent binary submission for «Application Name«. Before your app can be reviewed, the following issues must be corrected:

Invalid Icon Path — No icon found at the path referenced under key «CFBundleIcons»: icon114.png

Once these issues have been corrected, go to the Version Details page and click Ready to Upload Binary. Continue through the submission process until the app status is Waiting for Upload and then use Application Loader to upload the corrected binary.

The iTunes Store Team

I fixed this by adding two new keys to my entitlements plist — application-identifier and keychain-access-groups:

I got the «T9YRD11G97» from AppID in the provisioning profile, and the «com.duncancampbell.fontagious» from the BundleID in iTunesConnect.

Hope this helps.

When attempting to update my app, I experienced this problem as well. The only real change to my app since I last submitted it was the addition of iCloud support. I suspected something was wrong with my entitlements, and the error email I got from the itunesconnect@apple.com submit bot was very fishy. The relevant portion read:

I’ve anonymized the app/domain/team id here to MyAppName / mydomain.com / XXXXXXXXXX. Note that the complaint says «XXXXXXXXXXX.com.mydomain.myappmame» is incorrect. Indeed it is incorrect. It should be «myappname», not «myappmame» with an ‘m’ instead of ‘n’. I looked in the entitlement file in my project, and it was correct. I looked at the entitlement file included in the app bundle I submitted to the store, and it was correct. I unzipped the zip file I submitted to the store, and the entitlements file was correct there as well. So clearly this character substitution was happening after the app submission was accepted by the App Store.

Surely this problem doesn’t affect everyone, or there would be a mass outcry. So I figured it likely that there’s something «special» about my app that invokes a bug in the automated App Store submit processing. To verify, I created a new empty app from scratch, enabled iCloud entitlements, and submitted it to the App Store with a new app identifier. It was accepted and status changed to «waiting for review». So it passed muster. (I rejected the binary immediately so it wouldn’t be reviewed 🙂

I managed to work around the problem by changing my entitlements file:

My hope was that whatever code in the App Store that performs the team identifier prefix was the culprit, and was somehow corrupting a character farther down the string. By doing that substitution myself, perhaps the corruption wouldn’t occur and my app would go through. Surprise! It worked.

I wasted a day trying to figure this one out, and haven’t heard back from Apple support yet. But it’s sort of academic, since my app is now waiting for review. But I would still like to know what caused this, and that it’s been fixed by Apple. If I ever find out, I’ll update this posting.

Источник

Invalid Binary Error after App Store submission

I’m constantly getting the following Error:

after submitting my app to the App Store. I’ve tried everything recommended in Apple’s mail and also the answers to posts I found on Stackoverflow. Nevertheless I’m still getting this message. What could be my problem? What I’ve done so far:

• Checked to use App Store Distribution provisoning profile
• Checked that Entitlements.plist’s ‘can be debugged value’ is set to FALSE
• Cleaned up my project
• Deleted the directory containing my app (the build directory I guess)
• Set my scheme to use the Release Build Configuration for Archiving

Is there something I have missed? I’m going nuts after my 20.-something submission 🙁

4 Answers 4

Your not using the correct certificates when building your app. Delete your certificates in Provisioning Portal and create new ones and update them in Xcode. Goto Organizer / Provisioning Profiles / Refresh and allow Xcode to fetch the latest ones.

Again, clean all of your targets. You can even go to /Users/%USERNAME%/Library/Developer/Xcode/DerivedData and delete all of the directories in there (mainly your app in question).

Then Under TARGET in Xcode, goto Build Settings and choose the NEW certificates.

Also, use Archive *(under Product in Xcode 4.0+)* in Xcode. When the build is complete, Organizer should open to your Application Archives , if not, go there and click on Archives. Select your app and choose Validate. , once your app is validated, click Submit. .

Источник

iTunes Connect: Invalid binary

I am getting this error in iTunes Connect .

I have an app and I make some changes in that. So now I am uploading the updated version with the Organizer, but after upload, I am getting » invalid binary «, but no more information. Looking into this forum I found many people face same issue but no solution works for me.

I validate the app before uploading and the validate process is OK.. any advice will be welcome, this is driving me crazy.

thanks in advance.

Titanium SDK 5.5.0 GA

4 Answers 4

Whenever you get an invalid binary error an email gets sent to the itunesConnect account, with the explanation on why it is invalid.

I did receive an invalid binary message and contained the following message:

This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSAppleMusicUsageDescription key with a string value explaining to the user how the app uses this data.

So it does have to do with a permission request. The way to fix this issue is to check the email, and explain why you are requesting access to that privacy-sensitive data. Keep in mind that we are not using Apple Music, but for some reason that showed up there 😉

I get this email from Apple:

This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data.

This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSMicrophoneUsageDescription key with a string value explaining to the user how the app uses this data.

This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSCameraUsageDescription key with a string value explaining to the user how the app uses this data.

This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSAppleMusicUsageDescription key with a string value explaining to the user how the app uses this data.

Once these issues have been corrected, you can then redeliver the corrected binary.

My App is using the camera, not Apple Music, not Agenda, etc. Maybe one of the Modules.

Источник

Xcode 10 GM — Invalid Binary Architecture when submitting to App Store Connect?

I have an iOS and watchOS app that support iOS 11/12 and watchOS 4/5. I’ve been submitting builds to App Store Connect for TestFlight without issue using the Xcode 10 betas. Today I submitted a build using Xcode 10 GM, and I got the following email:

We identified one or more issues with a recent delivery for your app, «littlefeed». Please correct the following issues, then upload again.

Invalid Binary Architecture — iOS 3.0 introduced support for multiple binary architectures. If your binary is built for multiple architectures, your Info.plist must have a MinimumOSVersion key with a value of at least 3.0. Additionally, if your app is intended to support earlier iPhone and iPod touch models, your app must contain at least an armv6 binary; «thin» armv7-only binaries will not be accepted unless the armv7 required device capability is also present in the Info.plist UIRequiredDeviceCapabilities key or the MinimumOSVersion key has a value of 4.3 or higher.

The App Store Team

Problem is, this information is terribly out of date. The MinimumOSVersion key has long been deprecated; armv6 is an irrelevant architecture for iOS 11+ devices; the link to QA1707 is dead; etc. All related issues on Google and Stack Overflow tend to date back to 2012 or earlier, so I don’t actually know what the issue is. My best shot-in-the-dark is that it’s related to the fact that the Apple Watch Series 4 is now a 64-bit processor, and maybe I need to configure my watch app and watch extension targets somehow to handle it?

If anyone has any thoughts, it’d be much appreciated.

Источник

Mac Store — Invalid Binary on iTunesConnect — the signature is invalid

iTunesConnect seem to be rejecting our binaries (for the Mac App Store) now with the following error

Invalid Signature — the main app bundle wetfm at path wetfm.app is signed but the signature is invalid. The following error(s) were reported from codesign:

a sealed resource is missing or invalid
In architecture: i386

I’ve spent the last several days now looking into this and have tried just about everything; the output from codesign —verify -vvvv wetfm.app is

wetfm.app: valid on disk
wetfm.app: satisfies its designated requirement

From codesign —display —verbose=4 wet.fm.app I get the full list of output headers, including Authority=3rd Party Developer Application: our company cert ; which seems to indicate it has been signed correctly.

The application is being built on the commandline (not XCode — using Unity3D) using codesign -vvvv -s ‘3rd Party Mac Developer Application: our company. ‘ —entitlements wetfm.entitlements wetfm.app ; then two plugin bundles and a framework are being signed using a similar command afterwards.

Finally the package is being built with productbuild —component «wetfm.app» «/Applications» —sign «3rd Party Mac Developer Installer: our company. » wetfmpackage.pkg — which is then being submitted through Application Loader (which accepts it, uploads, then the invalid signature email is sent to us.)

So far, I’ve tried all the following:

• Revoking all our developer certificates, regenerating them within XCode (and seperately via the Developer Certificates site)
• Deleting all provisioning profiles
• Re-arranging the order of the signing process (signing the main bundle first, last)
• Signing or not signing the sub bundles (which come up as additional errors later if they are not)
• Adding ‘application-identifier’ to the entitlements file (caused Application Loader to reject upload)
• Renaming the app and bundleIDs (from wet.fm to wetfm)
• Trying to upload to a new (different) app on iTunesConnect

As best I can tell, it does appear to be being signed correctly locally — it’d be extremely useful if I could get codesign to at least output the same error message as the one being emailed back; as that would make testing significantly faster.

If anyone has any clues or insights, it’d be extremely appreciated. Thanks!

(Environment: 10.8.2, latest versions of everything.)

Источник