Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

Reply to ITMS-90338: Non-public API usage and ITMS-90426: Invalid Swift Support in Expo
Any Update? I also had an issue related to Invalid Swift Support. This was a minor change from a version that passed review a few days earlier, and now the binary is invalid. Our issue was: ITMS-90433: Invalid Swift Support - The file libswift_Concurrency.dylib doesn't have the correct code signature. The previous build was Xcode 13.2.1, and we can't build on Xcode 14 due to a dependency that needs to be updated.
Sep ’22
Reply to [SKStoreProductViewController sceneDisconnected:] crash on iOS 15.7
I'm seeing this issue in one of the apps I work on. I saw it first in crashlogs (Bugsnag) in July but last 2 weeks the number of reported crashes skyrocketed. The app doesn't explicitly use the SKStoreProductViewController. It uses UIApplication.shared.open(itms-apps://apps.apple.com/app/appid) and the SKStoreReviewController.requestReview(), I'm not sure which one of these uses the SKStoreProductViewController. What is very odd, the other 2 apps that use the same way to show the other product app pages don't have this crash in their logs. Edit: I saw somebody mentioned the issue could be related to AdMob. This app also uses AdMob, the other 2 apps don't use AdMob.
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’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
[iOS16] The value of bundle-identifier key can no longer be used as *.
Hi team. I've always used the manifest download link to install my test app like itms-services://?action=download-manifest&url=https://host.sample/sampleManifest.plist However, at the iOS 16, it was found that installation errors occurred when the value of the bundle-identifier of the manifest was set to * like <key>metadata</key> <dict> <key>bundle-identifier</key> <string>*</string> </dict> and install error logs are : item being installed did not contain an app with bundle ID “*”, but it did contain app(s) with bundle ID ${real bundle id} I wonder if there is a way to use it instead of real app bundle id like '*'. thanks.
4
0
1.6k
Sep ’22
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
Sep ’22
ITMS-90482 & ITMS-90630
Hi, Yesterday I updated Xcode to v14.0. Today I submited an app and got these errors: We identified one or more issues with a recent delivery for your app, XPTO 1.95.3 (0.139). Please correct the following issues, then upload again. ITMS-90482: Invalid Executable - The executable 'XPTO.app/XPTO' contains bitcode. ITMS-90630: Invalid Executable - The executable 'XPTO.app/XPTO' does not contain compiled code Bitcode is set to YES on Build Setting -> Build Options -> Enable Bitcode Does anyone know how to fix?
1
0
2.3k
Sep ’22
WidgetKit Extension Causing "ITMS-90078: Missing Push Notification Entitlement"
Hello! We have a pretty robust codebase that has APNs enabled for the base app. We recently added a WidgetKit extension to replace our old widget from pre-iOS 14. Our working provisioning profiles (before this addition) were generally as such: Our main target has APNs enabled and configured (and has for ~6 years), testing push notifications on our previous release works as intended Our old widget does not have APNs enabled, since it doesn't support push notifications What we added was: 3. A new iOS14+ widget extension without APNs enabled Ever since we added the third provisioning profile, we've received the warning: ITMS-90078: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the 'aps-environment' entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a
0
0
2.1k
Sep ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Still here: (React native) ITMS-90338: Non-public API usage - The app references non-public selectors in App: _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, onSuccess:. 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.
Sep ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
the message I got yesterday (12th Sept 2022) was: ITMS-90338: Non-public API usage - The app references non-public selectors in Advantis.iOS: checkFocusGroupTreeForEnvironment:, commissioningComplete:, pairDevice:address:port:discriminator:setupPINCode:error:, setListenPort:, sharedController, sleep:, test:, toggle:. 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 Is this really STILL ongoing???
Sep ’22
ITMS - 90338: Non -public API usage
ITMS - 90338: Non -public API usage - The app references non-public selectors in xfApp1.iOS: accessibilityBrailleMapRenderRegion, accessibilityBrailleMapRenderer, activePlayer, beginAuthorizationWithRequest:, cancelAuthorizationWithRequest:, checkFocusGroupTreeForEnvironment:, commissioningComplete:, connectionTypesMask, pairDevice:address:port:discriminator:setupPINCode:error:, playerId, serviceExtensionWillTerminate, session:didReceiveData:fromPlayer:, session:didReceiveMessage:withData:fromPlayer:, session:player:didChangeConnectionState:, session:player:didSaveData:, setAccessibilityBrailleMapRenderRegion:, setAccessibilityBrailleMapRenderer:, setConnectionTypesMask:, setListenPort:, sharedController, sleep:, test:, toggle:. 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 inclu
0
0
582
Sep ’22
ITMS-90338: Non-public API usage and ITMS-90426: Invalid Swift Support in Expo
Hello, I tried to push a build to TestFlight and received these two errors a few weeks ago. Dear Developer, 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 selectors in : _isKeyDown, _modifiedInput, _modifierFlags, determineAppInstallationAttributionWithCompletionHandler:, handleNotification:, isPassthrough, lookupAdConversionDetails:, onSuccess:, removeValuesForKeys:completion:, transform:, viewManager. 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/ ITMS-9
3
0
1.5k
Aug ’22
ITMS-90338: Non-public API usage
ITMS-90338: Non-public API usage - The app references non-public selectors in myApp _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, isPassthrough, onSuccess:, removeValuesForKeys:completion:. 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.
4
0
2.1k
Aug ’22