Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

Reply to ERROR ITMS-4238: "Redundant Binary Upload"
ERROR ITMS-90478: Invalid Version. The build with the version “4.4” can’t be imported because a later version has been closed for new build submissions. Choose a different version number.ERROR ITMS-90186: Invalid Pre-Release Train. The train version '4.2' is closed for new build submissionsERROR ITMS-90062: This bundle is invalid. The value for key CFBundleShortVersionString [4.2] in the Info.plist file must contain a higher version than that of the previously approved version [4.4].Il file di analisi API risultante è troppo grande. Non siamo in grado di convalidare l'uso API prima della distribuzione. Questo è solo un messaggio informativo.
Jun ’15
ITMS-4238: "Redundant Binary Upload"
I understand that this error is because Organizer is submitting a binary with the same version number, but I have changed the version numbers. I've done the homework and looked up similar forum posts on this error, but the problem is not as simple as incrementing the build number.Here's what I did:My current version in the store is 2.0.4In iTunesConenct, I created a new version submission for 2.1.0. I filled out all fields (except Build) and clicked Save. It is now marked Ready for Submission.In Xcode, I changed the Version to 2.1.0 and the Build to 2.1.0.In Xcode, I built and ran the app. It works!I opened Organizer. In Archives, it shows Version 2.0.4, and my last submission was months ago.In Organizer, I clicked Submit and followed the steps. I got the Redundant Binary error that 2.0.4 already exists.To double-check, I opened my -Info.plist file and it shows both Bundle Version and Bundle Versions string, short as 2.1.0To triple-check, I looked in my Target > Build Settings > Packaging. I can see tha
0
0
306
Nov ’15
ITMS-90283 invalid provisioning profile
I have a maccatalyst App on the store, uploaded 20 March. Am now attempting to upload a new version but it fails with:Unable to process application at this time due to the following error: Invalid Provisioning Profile. The provisioning profile included in the bundle maccatalyst.com.plugh.XYZZY [maccatalyst.com.plugh.XYZZY.pkg/Payload/XYZZY.app] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer PortalAs I mentioned this App is already on the store and nothing has change in the project relating to profiles/signing to my knowledge other than a new Xcode. In fact, signing and provisioning is all automatic, and the maccatalyst app id is auto-generatedInterestingly, I still have the previous App bundle that was successfully uploaded to the store, and when I (re-)verify it there is an identical error to the above. So I am at a loss as to how to move ahead at this point in time.
3
0
3.2k
May ’20
ITMS-91061: Missing privacy manifest
Hi all, Im trying tu publish an app for iOS and I get it rejected by the lack of this privacy manifest, but unless I understood this wrong, this manifest is needed for external tools used, or maybe Im wrong, Im publishing an app made in Unity, so in this case, one has to include a privacy manifest by default? Sorry Im lost in all these terms, so I don't know if im asking something redundant, if you know how to fix this issue please tell me or direct me to the process because I haven't been able to identify the issue. Thanks a lot for any clue beforehand really
0
0
142
Jun ’25
ITMS-90034: Missing or invalid signature
After uploading a new App to the App Store Connect i receive an e-mail stating:ITMS-90034: Missing or invalid signature - The bundle '...' at bundle path 'Payload/...' is not signed using an Apple submission certificate.The App don't use any capability.I've used Xcode to upload, as in a previous App which now is on the App Store.All the apps use the default configuration: Automatically manage signing, Provisioning profile Xcode Managed Profile, Signing Certificate Apple Development: ############The requested Signing Certificate is present in the keychain in 3 versions, the last one is valid (the older 2 are revoked).What I should correct?
117
0
58k
Jun ’20
ITMS-90561: Invalid Swift Support - The watchOS application has Swift libraries at both
I recently tried to submit an update to an app that I have been constantly updating; the last update was done two months ago using Xcode 11 and I had no issues back then. This time when I Distributed the App using Xcode 12, everything went smoothly without any errors but after a few minutes, I got the following email from Apple. Dear Developer, We identified one or more issues with a recent delivery for your app, “My App” 6.2 (6.2). Please correct the following issues, then upload again. ITMS-90561: Invalid Swift Support - The watchOS application has Swift libraries at both /Payload/My App.app/My App Watch App.app/My App Watch App Extension.appex/Frameworks/ and /Payload/My App.app/My App Watch App.app/Frameworks/. Remove all of the Swift libraries from one of the locations and resubmit your app. Best regards, The App Store Team Any idea what should I be removing?
1
0
1.3k
Oct ’20
AppStore Connect Operation error - Error ITMS-90168 : "null"
Hello, I am uploading an update of a test flight and it gives me this error in the final part. :( It gives me the following legend in xcode app store connection operation error error itms-90168: null In the Packaging record that is generated.... Failed for distribution item with error Error Domain=IDEFoundationErrorDomain Code=1 It generates that error right at the end, at the moment of finishing uploading the .ipa. It generates a registry folder where the .ipa and several files come out. Does anybody know what is it due to? Thanks in advance I will leave a little code of the last lines of the log with the idea that it can help something 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 [OPTIONAL] Can't have a profile, not a bundle at 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 Process
0
0
1.5k
Feb ’22
ERROR ITMS-90283: “Invalid Provisioning Profile” in Mac-Catalyst app
I'm working on a Mac-Catalyst app. It needs to access some of the AppKit Classes so I integrated a macOS Bundle to accomplish that(reference blog post: https:// medium.com/better-programming/how-to-access-the-appkit-api-from-mac-catalyst-apps-2184527020b5), and it works fine except it won't let me upload the app to the Appstore. When I try to upload the app XCode throws me an error: ERROR ITMS-90283: Invalid Provisioning Profile. The provisioning profile included in the bundle com.XXX.MacPlugin [com.XXX.XXXX.pkg/Payload/XXX.app/Contents/PlugIns/MacPlugin.bundle] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer Portal. I tried uploading the build removing this plugin and it worked, but with this Plugin it won't work.
0
0
636
Feb ’21
ITMS-90899 : how to select macOS 12.4 or macOS 12.5 when submitting iOS app
I received this message when submitting my app : ITMS-90899: Apple silicon Mac support issue - The app is not compatible with the provided minimum macOS version of 12.4. It can run on macOS 13.0 or later. Please specify an LSMinimumSystemVersion value of 13.0 or later in a new build, or select a compatible version in App Store Connect. There is now possibility to select macOS 12.5, 12.5 or even 13 with xCode 13.4.1 and on Apple Store Connect The app is running correctly on macOS 12.5.1 (but even this version is not selectable) Can someone help me understand.
2
0
7.6k
Aug ’22
ITMS-90683: Missing Purpose String in Info.plist, but NSUserTrackingUsageDescription is set in InfoPlist.strings
Hello, when uploading a build to AppStoreConnect we got this issue: ITMS-90683: Missing Purpose String in Info.plist - Your app‘s code references one or more APIs that access sensitive user data. The app‘s Info.plist file should contain a NSUserTrackingUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources Its correct that we don't have NSUserTrackingUsageDescription but it is set in InfoPlist.strings and our QA verified it is working for all supported languages. Do we need to add NSUserTrackingUsageDescription to the plist, but then its not localised? Or is there some ghost language that is not being set correctly (i.e. en-US, e
2
0
2.6k
Sep ’22