Search results for

“ITMS-90338”

1,703 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
308
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
148
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
How to fix the _ADBannerContentSizeIdentifierLandscape, _ADBannerContentSizeIdentifierPortrait non-public symbols in app get error in app store upload.
We identified one or more issues with a recent delivery for your app, App name. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public symbols in App name: _ADBannerContentSizeIdentifierLandscape, _ADBannerContentSizeIdentifierPortrait. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ Get above error message app store when upload the app too app store, i removed the iAd.framework reference related all pods and library but still i got same error email. Any have solution for this error, please share your thoughts.., Thanks.
3
0
1.2k
Jun ’21
Can't post application to appstore
every time i am trying to post my application to appstore I got this message: ITMS-90338: Non-public API usage - The app references non-public selectors in XXXX: setNavigationBar:. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ I search inside my code and my 3rd party libraries about setNavigationBar and navigationbar = but i didn't find any matched results. i tryed to exported the application build and i searched inside the exported build abdout setNavigationBar and found one result in but couldn't find any details about location or file that generated this. what to do?
4
0
444
Nov ’24
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
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing
I have recently added some Swift files to my Objective C project that I had been successfully publishing to the AppStore. I'm able to debug on my devices and simulators but when submitting to AppStoreConnect I get the following email: Dear Developer, We identified one or more issues with a recent delivery for your app, ...... . Please correct the following issues, then upload again. ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Best regards, The App Store Team From the internet I gather the following build settings are required for the project but that doesn't seem to help my case: 1. Defines Module -> YES 2. Always embed Swift Standard libraries -> YES To reproduce the problem, do the following: Create new Objective C project in XCode Add a single Swift file and choose YES when prompted to make the bridging header Set Defines Module and Always embed Swift Standard libraries to YES in buil
0
0
2.4k
Oct ’22
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
Reply to Xcode 11 beta 6 upload error
finally I solved the issue with this link: https://stackoverflow.com/a/58552091/1505074deleted the folder /usr/local/itms/ with the ancient Transport in it.
Replies
Boosts
Views
Activity
Nov ’19
Reply to UIUserInterfaceStyle key invalid
You are not alone.ERROR ITMS-90190: Invalid Info.plist Key. The key 'UIUserInterfaceStyle' in the Payload/brownie.appInfo.plist file is not valid.
Replies
Boosts
Views
Activity
Aug ’19
Reply to ITMS-90000: This bundle is invalid - $message.
ITMS-90000: This bundle is invalid - $message. Happening for over 24 hours now for me. Tried 3 times. Berlin.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jan ’21
Reply to itmstransporter 3.0.0 broken in Linux.
Some other uses of itms transporter were turned off at the start of November. Maybe this is collateral damage? Have any of you submitted support requests?
Replies
Boosts
Views
Activity
Nov ’22
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.
Replies
Boosts
Views
Activity
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
Replies
0
Boosts
0
Views
308
Activity
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.
Replies
3
Boosts
0
Views
3.2k
Activity
May ’20
ITMS-90426: Invalid Swift Support
Hi, I receive the following mail after the upload of my app form xCode to the Apple Connect platform. Before uploading, I correctly validate the version, and xcode gives me the validation. Do someone know how resolve this issue? Thanks in advance
Replies
0
Boosts
0
Views
784
Activity
Jan ’23
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
Replies
0
Boosts
0
Views
148
Activity
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?
Replies
117
Boosts
0
Views
58k
Activity
Jun ’20
How to fix the _ADBannerContentSizeIdentifierLandscape, _ADBannerContentSizeIdentifierPortrait non-public symbols in app get error in app store upload.
We identified one or more issues with a recent delivery for your app, App name. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public symbols in App name: _ADBannerContentSizeIdentifierLandscape, _ADBannerContentSizeIdentifierPortrait. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ Get above error message app store when upload the app too app store, i removed the iAd.framework reference related all pods and library but still i got same error email. Any have solution for this error, please share your thoughts.., Thanks.
Replies
3
Boosts
0
Views
1.2k
Activity
Jun ’21
Can't post application to appstore
every time i am trying to post my application to appstore I got this message: ITMS-90338: Non-public API usage - The app references non-public selectors in XXXX: setNavigationBar:. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ I search inside my code and my 3rd party libraries about setNavigationBar and navigationbar = but i didn't find any matched results. i tryed to exported the application build and i searched inside the exported build abdout setNavigationBar and found one result in but couldn't find any details about location or file that generated this. what to do?
Replies
4
Boosts
0
Views
444
Activity
Nov ’24
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?
Replies
1
Boosts
0
Views
1.3k
Activity
Oct ’20
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing
I have recently added some Swift files to my Objective C project that I had been successfully publishing to the AppStore. I'm able to debug on my devices and simulators but when submitting to AppStoreConnect I get the following email: Dear Developer, We identified one or more issues with a recent delivery for your app, ...... . Please correct the following issues, then upload again. ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Best regards, The App Store Team From the internet I gather the following build settings are required for the project but that doesn't seem to help my case: 1. Defines Module -> YES 2. Always embed Swift Standard libraries -> YES To reproduce the problem, do the following: Create new Objective C project in XCode Add a single Swift file and choose YES when prompted to make the bridging header Set Defines Module and Always embed Swift Standard libraries to YES in buil
Replies
0
Boosts
0
Views
2.4k
Activity
Oct ’22
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
Replies
0
Boosts
0
Views
1.5k
Activity
Feb ’22