Search results for

“ITMS-90338”

1,703 results found

Post

Replies

Boosts

Views

Activity

ITMS-90237: The product archive package's signature is invalid. Ensure that it is signed with your '3rd Party Mac Developer Installer' certificate.
ITMS-90237: The product archive package's signature is invalid. Ensure that it is signed with your '3rd Party Mac Developer Installer' certificate. How can I solve? I've revoked my mac installer distribution certificate and re-download or did many things but the same error occurs several times.
2
0
946
Jul ’21
ERROR ITMS-90085: No architectures in the binary.
The app runs fine on the device and simulator and we are able to build an archive without any issues. The issue is when we want to upload the build to the app store using Xcode 12.5.1, we get the following error: App Store Connect Operation Error No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. Stackoverflow Link
1
0
2k
Jul ’21
Deeplink to specific watch face from browser
I see it is possible to open the Watch app from Safari or Chrome using itms-watchs:// or watchface://. I would like to be able to deep link to (open) a specific watch face from the browser. I see this is possible from other apps like Facer, because if you tap a watch face in that app and then tap the watch button, you will see this: https://imgur.com/jLDnbBl I would guess the Facer app is using a URL scheme like watchface://, so I just need to know how I can do the same thing. I tried something like watchface://https://mysite/mywatchfaceimage.png but it does not work (Safari cannot open the page because the address is invalid.).
2
0
1.5k
Jul ’21
Xcode 12 App Store Upload ERROR ITMS-90085: "No architectures in the binary. Lipo failed to detect any architectures in the bundle executable."
I recently updated to Xcode 12, and when I try to upload an archive to App Store Connect, I see this error: App Store Connect Operation Error ERROR ITMS-90085: No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. I can see that the .xcarchive's .app directory is missing an embedded framework's unix executable, whereas past successful .xcarchive files do have that executable. FWIW, BCSymbolMaps also has one less .bcsymbolmap file than usual. I've encountered this with Xcode 12 and 12.1. I have tried removing and re-embedding the framework, which made no difference. I addressed the issue for now by adding a build phase run script that copies the executable from ArchiveIntermediates into the .xcarchive, but was wondering if anyone has any ideas what's up with this. Is this an Xcode 12 bug?
2
0
2.4k
Jul ’21
Reply to Code Signing Error - Validating New Version
I have more details about the error I'm getting. Using the transporter app, I get the following error message: ERROR ITMS-90161: Invalid Provisioning Profile. The provisioning profile included in the bundle com.PeteTheGolfer.Annual [Payload/Bills & Periodicals.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal. I checked in the profile editor, and it says that I have a valid signing certificate. I'm really stuck and would appreciate any clues as to where to look next.
Topic: Code Signing SubTopic: General Tags:
Jul ’21
ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs
People have started receiving this warning on App submissions todayITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.Would be good to have more information about it, like an official deadline.Also the system used to warn is giving false positives, looks like it just searches for UIWebView word and doesn't really check if the app is using an UIWebView or not.
18
0
44k
Jul ’21
Xcode 13 upload results in ITMS-90338: Non-public API usage
I am trying to submit an app from Xcode 13 beta 1 to App Store Connect for internal TestFlight testing. After submission my binary is marked as invalid and I get the following email: ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in AppClips/App Clip.app/App Clip: NSConstantArray ,The app contains or inherits from non-public classes in Watch/WatchOS App.app/PlugIns/WatchOS Extension.appex/WatchOS Extension: NSConstantArray, NSConstantIntegerNumber Uploading the same app from Xcode 12 results in a successful submission. Feedback FB9157492. Anyone else with the same problem?
1
0
1.1k
Jul ’21
Reply to Xcode 13 upload results in ITMS-90338: Non-public API usage
I've got the same problem - ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in My_App_Name: NSConstantArray. But I tried building with Xcode 12 and the problem persists - I haven't included any new 3rd party frameworks since the last submission, but it's a huge project with quite a lot of them. At this stage I've also no idea how to track down exactly where this NSConstantArray is being found. Incredibly frustrating. Will watch this space...
Jul ’21
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
Error ITMS-90158 when using msal with Xamarin forms
I'm trying to publish a xamarin forms archive in Apple's App Store, however, I keep getting Error itms-90158 which states: The following URL schemes found in your app are not in the correct format: [msauth.com.companyname.blahApp://auth]. URL schemes need to begin with an alphabetic character, and be comprised of alphanumeric characters, the period, the hyphen, or the plus sign only. Please see RFC1738 for more detail. My [msauth...] is obviously not that which I put but I made sure that it was the same one I used in Azure B2C, furthermore, I made sure my bundle id in apple developer and in my Xamarin project had then exact same format (com.companyname.blahapp). I was wondering if this is uniquely a problem with using msal?? Or maybe I glanced over changing something? Any help would be very much appreciated. Thank you for your time.
1
0
684
Jun ’21
Problems with manually submitting a MacOS app to the Apple Store
Hello!I'm trying to submit a Java app to the Apple Mac Store, so I have to do this manually. I could fix 23 of 25 issues but I stuck on the last 2 😉ERROR ITMS-90230: Invalid product archive metadata. Error in keyPath [product-metadata.product-identifier]. Please re-build your archive with an up-to-date version of Xcode, and submit again.ERROR ITMS-90230: Invalid product archive metadata. Error in keyPath [product-metadata.product-version]. Please re-build your archive with an up-to-date version of Xcode, and submit again.For both of them I couldn't find anything useful in the net. What does ist mean and how to fix it???The result is the same in the Transporter app and when uploading manually in the terminal.Thanks in advance for any hint!Thomas
5
0
1.9k
Jun ’21
ITMS-90237: The product archive package's signature is invalid. Ensure that it is signed with your '3rd Party Mac Developer Installer' certificate.
ITMS-90237: The product archive package's signature is invalid. Ensure that it is signed with your '3rd Party Mac Developer Installer' certificate. How can I solve? I've revoked my mac installer distribution certificate and re-download or did many things but the same error occurs several times.
Replies
2
Boosts
0
Views
946
Activity
Jul ’21
ERROR ITMS-90085: No architectures in the binary.
The app runs fine on the device and simulator and we are able to build an archive without any issues. The issue is when we want to upload the build to the app store using Xcode 12.5.1, we get the following error: App Store Connect Operation Error No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. Stackoverflow Link
Replies
1
Boosts
0
Views
2k
Activity
Jul ’21
Deeplink to specific watch face from browser
I see it is possible to open the Watch app from Safari or Chrome using itms-watchs:// or watchface://. I would like to be able to deep link to (open) a specific watch face from the browser. I see this is possible from other apps like Facer, because if you tap a watch face in that app and then tap the watch button, you will see this: https://imgur.com/jLDnbBl I would guess the Facer app is using a URL scheme like watchface://, so I just need to know how I can do the same thing. I tried something like watchface://https://mysite/mywatchfaceimage.png but it does not work (Safari cannot open the page because the address is invalid.).
Replies
2
Boosts
0
Views
1.5k
Activity
Jul ’21
Xcode 12 App Store Upload ERROR ITMS-90085: "No architectures in the binary. Lipo failed to detect any architectures in the bundle executable."
I recently updated to Xcode 12, and when I try to upload an archive to App Store Connect, I see this error: App Store Connect Operation Error ERROR ITMS-90085: No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. I can see that the .xcarchive's .app directory is missing an embedded framework's unix executable, whereas past successful .xcarchive files do have that executable. FWIW, BCSymbolMaps also has one less .bcsymbolmap file than usual. I've encountered this with Xcode 12 and 12.1. I have tried removing and re-embedding the framework, which made no difference. I addressed the issue for now by adding a build phase run script that copies the executable from ArchiveIntermediates into the .xcarchive, but was wondering if anyone has any ideas what's up with this. Is this an Xcode 12 bug?
Replies
2
Boosts
0
Views
2.4k
Activity
Jul ’21
Reply to Code Signing Error - Validating New Version
I have more details about the error I'm getting. Using the transporter app, I get the following error message: ERROR ITMS-90161: Invalid Provisioning Profile. The provisioning profile included in the bundle com.PeteTheGolfer.Annual [Payload/Bills & Periodicals.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal. I checked in the profile editor, and it says that I have a valid signing certificate. I'm really stuck and would appreciate any clues as to where to look next.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’21
ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs
People have started receiving this warning on App submissions todayITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.Would be good to have more information about it, like an official deadline.Also the system used to warn is giving false positives, looks like it just searches for UIWebView word and doesn't really check if the app is using an UIWebView or not.
Replies
18
Boosts
0
Views
44k
Activity
Jul ’21
Xcode 13 upload results in ITMS-90338: Non-public API usage
I am trying to submit an app from Xcode 13 beta 1 to App Store Connect for internal TestFlight testing. After submission my binary is marked as invalid and I get the following email: ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in AppClips/App Clip.app/App Clip: NSConstantArray ,The app contains or inherits from non-public classes in Watch/WatchOS App.app/PlugIns/WatchOS Extension.appex/WatchOS Extension: NSConstantArray, NSConstantIntegerNumber Uploading the same app from Xcode 12 results in a successful submission. Feedback FB9157492. Anyone else with the same problem?
Replies
1
Boosts
0
Views
1.1k
Activity
Jul ’21
Reply to Xcode 13 upload results in ITMS-90338: Non-public API usage
I've got the same problem - ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in My_App_Name: NSConstantArray. But I tried building with Xcode 12 and the problem persists - I haven't included any new 3rd party frameworks since the last submission, but it's a huge project with quite a lot of them. At this stage I've also no idea how to track down exactly where this NSConstantArray is being found. Incredibly frustrating. Will watch this space...
Replies
Boosts
Views
Activity
Jul ’21
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
Error ITMS-90158 when using msal with Xamarin forms
I'm trying to publish a xamarin forms archive in Apple's App Store, however, I keep getting Error itms-90158 which states: The following URL schemes found in your app are not in the correct format: [msauth.com.companyname.blahApp://auth]. URL schemes need to begin with an alphabetic character, and be comprised of alphanumeric characters, the period, the hyphen, or the plus sign only. Please see RFC1738 for more detail. My [msauth...] is obviously not that which I put but I made sure that it was the same one I used in Azure B2C, furthermore, I made sure my bundle id in apple developer and in my Xamarin project had then exact same format (com.companyname.blahapp). I was wondering if this is uniquely a problem with using msal?? Or maybe I glanced over changing something? Any help would be very much appreciated. Thank you for your time.
Replies
1
Boosts
0
Views
684
Activity
Jun ’21
Reply to ITMS-90725 with xcode 12.4
I have facing same issue from today. i have try and clean up derived folder but doesn't work. ERROR ITMS-90725: “SDK Version Issue. This app was built with the iOS 13.7 SDK. All iOS apps submitted to the App Store must be built with the iOS 14 SDK or later, included in Xcode 12 or later.”
Replies
Boosts
Views
Activity
Jun ’21
Reply to Manage subscriptions
This URL worked for me with iOS 14.4 itms-apps://buy.itunes.apple.com/WebObjects/MZFinance.woa/wa/manageSubscriptions
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
Jun ’21
Problems with manually submitting a MacOS app to the Apple Store
Hello!I'm trying to submit a Java app to the Apple Mac Store, so I have to do this manually. I could fix 23 of 25 issues but I stuck on the last 2 😉ERROR ITMS-90230: Invalid product archive metadata. Error in keyPath [product-metadata.product-identifier]. Please re-build your archive with an up-to-date version of Xcode, and submit again.ERROR ITMS-90230: Invalid product archive metadata. Error in keyPath [product-metadata.product-version]. Please re-build your archive with an up-to-date version of Xcode, and submit again.For both of them I couldn't find anything useful in the net. What does ist mean and how to fix it???The result is the same in the Transporter app and when uploading manually in the terminal.Thanks in advance for any hint!Thomas
Replies
5
Boosts
0
Views
1.9k
Activity
Jun ’21
error no .app bundles found in the package
Why would I get an error when I'm uploading the app using the Xcode organizer that says the following?ERROR ITMS-90167: No .app bundles found in the package
Replies
5
Boosts
0
Views
6.9k
Activity
Jun ’21
Downgrade minimum system version
Hello, I have a published app with minimum system version 8, and by mistake I uploaded a new build with minimum system version 14.5 I tried to upload another build with correct minimum system version but I got the following error: Error ITMS-902080: invalid bundle. The bundle dose not support the minimum os version specified in the info.plist
Replies
1
Boosts
0
Views
514
Activity
Jun ’21