Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

Reply to App Sandbox not enabled
I was welcomed with this issue today. Been publishing this app properly signed for years. It's even visible in the package review that the binaries have this flag enabled but the build is being blocked with this message: ITMS-90296: App sandbox not enabled The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[com.aone.keka.pkg/Payload/Keka.app/Contents/MacOS/keka7z ...
Topic: Code Signing SubTopic: General Tags:
May ’23
ITMS-90725: SDK Version Issue
While deploying the apps to app store connect, I am getting a mail from app store connect stating: ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. For context, my minimum deployment version is set to 15.0 and building the apps with xcode 13.4 (ios 15.5). Can anyone please help me with this.
8
0
20k
May ’23
Reply to When does “Waiting for Review” show in App Connect
I discovered this for my tvOS version of my App (iOS version is okay): We identified one or more issues with a recent delivery for your app, Monster Paddle Pong 1.2 (8). The following are for your information only and do not require any action: ITMS-90471: Missing Image Asset - Your app is missing the Top Shelf Image Wide 2x asset in 'Payload/Monster Paddle tvOS Game.app'. The do not require any action statement confuses me because until I correct the Missing Image Asset error, my new Version = 1.2 will not be uploaded for Review. This error is new for me that did not appear 2 months ago when I started with version 1.0 Nevertheless, I did correct it by adding the 2x asset as requested and then Archived again. This time, however, I did not get a 2x asset error email, so I assume the App Connect Site was happy because the email I did get was: The following build has completed processing: Platform: tvOS App Name: Monster Paddle Pong Build Number: 9 Version Number: 1.2 App SKU: 5683766467 App Apple ID: 1
May ’23
Direct link to all my apps in App Store not working in iOS 12
In previous iOS versions I've able to open a URL of the form itms-apps://itunes.apple.com/artist/id463855590 and the App Store app would open at a page showing all my apps. This doesn't seem to work in iOS 12. I see a Cannot Connect to AppStore error message within the App Store app.Using https instead of itms-apps takes me to the iTunes Store app and does show a list of my apps, but as a simple list, not the nice iOS 11 app store UI.Opening an itms-apps URL for a specific app still seems to work (but not 100% of the time).Is this just a temporary problem during the beta or are links to artist pages no longer supported?
15
0
46k
May ’23
Azure auth URL not supported
ERROR ITMS-90158: The following URL schemes found in your app are not in the correct format: [msauth.com.client.timesheetapp://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. Plist contain this URl : msauth.com.client.timesheetapp://auth which is not supported. any suggestion what is the correct format for it. Thank you
1
0
793
May ’23
The right way to extend UIRequiredDeviceCapabilities
I've added NFC support for my app. So, my UIRequiredDeviceCapabilities were extended from armv7 to armv7 nfc. This means I've prevented this application from running on devices supported by previous versions. Now I've received a message from Apple: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. What is the right way to add new functions?
1
0
885
May ’23
SDK Version Issue message that defies basic math
We got this message after publishing our app to test flight: ITMS-90725: SDK Version Issue - This app was built with the iOS 16.0 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. I'm no math genius but am pretty sure that 16 is greater than 15. Why did I get this messages? Can I ignore it? will it prevent my app from being able to be submitted to the app store?
10
0
10k
May ’23
ITMS-90338: Non-public API usage
ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/ They haven't mentioned Non-public APIs which we have used how can we resolve it? How can we resolve with this information?
3
0
983
Apr ’23
Bulk IAP Management / iTMSTransporter Issue
Do any Apple tools exist that currently enable Bulk IAP management? I have been trying to use the iTMSTransporter, and the following command does respond appropriately, but the metadata.xml that is returned is incredibly bare, and does not include any of the 50+ IAPs we have in our app. ./Transporter.app/Contents/itms/bin/iTMSTransporter -m lookupMetadata -u *** -p *** -destination ~/Desktop/IAP -apple_id *** -app_platform ios -subitemtype InAppPurchase
1
0
649
Apr ’23
ITMS-90426: Invalid Swift Support
After using iOS16's new feature AppIntents, AppStore review is failed: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. I tried all methods in internet, but they all not work. Such as: I'm using the public version of Xcode I'm not using Ad hoc cert or .pp file I tried archive manually without using fastlane I tried change the Always Embed Swift Standard Libraries The only changes is iOS16's AppIntents. Before i use AppIntent, it works fine. After i use AppIntent, it failed. Only one commit between 2 .ipa. Can anyone help me? Many thanks.
1
0
1.4k
Apr ’23
Major issue on upload new version
I have 3 non universal apps and i get this:ERROR ITMS-90101: This bundle does not support one or more of the devices supported by the previous app version. Your app update must continue to support all devices previously supported. You declare supported devices in Xcode with the Targeted Device Family build setting.App app versions on the app store are NOT universal and iphone only. / except the latest released build.Someone NOT me has changed the device support from iphone only to universal and now im stuck.There is an faq: https://developer.apple.com/library/content/qa/qa1623/_index.htmlChoices 1 and 3 are not an option for me.Choice 2 is not working : i have changed min. iOS from 9.0 to 9.1 and i get the same error.Customer satisfaction should be the main goal!! Or not?I need help from a apple engineer to fix this.Thanks
2
0
16k
Apr ’23
ITMS-90432: Issue while uploading app to appstore.
We are trying to upload new build for our already existing app to appstore, with a build script to embed framework(Which is just copying from build directory to MyApp.app/Frameworks). Everything builds and works fine in my local machine. But getting this error while uploading to appstore. ITMS-90432: Invalid Swift Support - The file MyApp.app/Frameworks/Framework1.framework, MyApp.app/Frameworks/Framework2.framework doesn’t have the correct file type for this location. Ensure you’re using the correct file, rebuild your app using the current public (GM) version of Xcode, and resubmit it. We are copying to the correct directory, but still getting the above error while uploading. Are we missing the obvious here?
1
0
738
Apr ’23
CFBundleIdentifier not match?
I submitted a test package and got the following email: ITMS-90345: Metadata/Info.plist Mismatch - The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in test [net.neolib.test.pkg/Payload/test.app]. I really don't have any idea what's wrong. It's a simple (almost blank) app with nearly no modification (except linked with a dylib). What is the metadata.xml? I cannot find it in my test project.
2
0
857
Apr ’23
Getting The bundle uses a bundle name or display name that is already taken ERROR while pushing for Testflight
Hi, I'm getting this error while pushing my app for testflight Dear Developer, We identified one or more issues with a recent delivery for your app, MyAppName 1.4.24 (1). Please correct the following issues, then upload again. ITMS-90129: The bundle uses a bundle name or display name that is already taken. Best regards, The App Store Team I've been abled to push version 1.4.16, 1.4.17, 1.4.19, 1.4.20 successfully before with no issues, and I'm sure I'm still holding the bundle identifier but yet this error is still appearing everytime I try to upload a new build. I'm wondering if anyone else having the same problem?
1
0
2.7k
Mar ’23