I have App Store Connect issues, after when I transferred application another account. ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['oldID.iosapp'] and the new version of software being submitted has an application-identifier of ['newID.iosapp']. This will result in a loss of keychain access. development team changed and what can I do ?
ITMS-90338
1,571 results found
Post
Replies
Boosts
Views
Activity
This error is reaction on new build created and uploaded to AppStore with new project but same bundleId/displayName/signingInfo. Here is the scenario with symbolic values to explain it better: Build #1 (Version 1.0) project: P1 Bundle id: com.some.app Display name: My App Signing info: TeamX, CertificateX (automatic signing) I had to move the app to new project with completely new targets/configs/sources but same app metadata. Build #2 (Version 1.0) project: P2 (new) Bundle id: com.some.app Display name: My App Signing info: TeamX, CertificateX (automatic signing) So you can see that all is changed but the important app metadata (BundleId, DisplayName, Signing info) remained the same. Yet the upload of build 2 results with: ITMS-90129: The bundle uses a bundle name or display name that is already taken Note that the Build #2 showed in AppStoreConnect / TestFlight / iOS Builds / Version 1.0 for a few seconds as Processing but than disapeared with the error. Thus Apple tries to add the new build #2 it
Hi, I always received an email with ITMS-90078: Missing Push Notification Entitlement after distributing the app bundle to app store connect. But I have not used push notifiction in my app. Anyone can help on this?
I have created iOS enterprise app that is not installing using the dropbox url. The app is no longer able to be installed using the itms-services://?action=download-manifest&url=https://dl.dropboxusercontent.com/scl/fi/34j34hj37vl4defedon43hgi/appname.plist?rlkey=bz6sjxhlf349pn7rjk&raw=1. I tried in 2023 year and it worked then. with the URL like - itms-services://?action=download-manifest&url=https://dl.dropboxusercontent.com/s/dz2feq4234h3g4an5/appname.plist . Our Enterprise certificate and provisioning profiles are up to date and valid. I was able to install the app into simulator and iPhone using Xcode. The dropbox links are all shared and accessible to anyone with the link. I can download my IPA file and plist file with no issue if I browse to the URL directly, but it just doesn't work with the itms-services://?action=download-manifest& Does Apple still support OTA installs for enterprise developers? What else can I do to troubleshoot?
Here is a symbolicated file DigiDeals-2024-07-23-150203_symbolicated.txt this is the code in AppDelegate didFinishLaunchingWithOptions that calls displayMessages which is where the app seems to crash Task{ await universal.displayMessages() } this is the displayMessages() code with the line it seems to crash at in bold. Again, the alert shows and when OK is selected (only when app is first opened after download otherwise the app just goes to the home screen when OK is selected) the popUpZipCode() (underlined below) runs. The app seems to crash only when the app first runs after download. func displayMessages() async{ var inf: Information = Information(Message: , MsgType: ) var buttonText: String = OK //if (!msgDisp && allowNotifications){ if (!msgDisp){ do { let querySnapshot = try await db.collection(AppInfo).getDocuments() for document in querySnapshot.documents { //print((document.documentID) => (document.data())) ///// your code if (document[MsgType] as! String == I){ inf.Message = document[Me
I have built my app with no errors and uploaded to testflight successfully. But when I try to install my app on my iphone, it throws the following error. Could not install {AppName} the requested app is not available or doesn't exist. And also received an email saying 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. ... But I already have the required provisioning profile and have 'aps-environment' entitlement manually. What is the reason and please let me know potential solutions.
Hi, Can someone please help me with the below issue, I validated the app before distributing from Xcode, and it passed. but I received a mail from Apple Developer Relations saying there a problem, but I don't have any clue how to solve this problem. ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftMetal.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/connectdots.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. I dont know where these dylibs are now and how to move them. Also I am using Xcode 15.3. what does it mean current public version of Xcode Thanks in Advance, Thirupathi.
@endecotp We are facing the same issue. We tested the app and everything works fine. We do get the email from App Store Connect saying - Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. 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. Refer to QA1623 for additional information: https://developer.apple.com/library/ios/#qa/qa1623/_index.html The app was uploaded successfully, but is stuck on Waiting for Review since. Does this issue block us from publishing our update / new Build ?
So I have an app live in the app store all good, however I am now developing an update to it that adds the ability to allow photos to be used and that requires that the app gets an additional access to the camera roll. Now on upload to testflight I get this error emailed to me, not in the interface: 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. To me that is saying that I cant add new features to an app that requires additional permissions. Is that correct? How can I get around this, will my app get rejected when I submit it due to this, or is it just an information item?
Hi,I used the following documentation: https://developer.apple.com/documentation/storekit/in-app_purchase/testing_promoted_in-app_purchases to test in-app purchase workflows initiated from the app store promotions. The test URL (itms-services://?action=purchaseIntent&bundleId=com.example.app&productIdentifier=product_name) worked just fine with a development build as it launched the app and initiated the purchase process but when I tried to use it with an app store build it didn't work (app would not launch). Is this the expected behavior? And if so, is there a way to test the workflow with app store builds before I enable the app store promotions?
It seems to work for me, however I would like to show a certain screen when the app is opened through the itms-services://?action=purchaseIntent... URL. But when I tap the URL none of my App Delegate life cycle funcs are being called, except applicationWillResignActive, but can't read the information in the URL. Is there a way to read out the intent and productID when the app is being opened this way?
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.
Hi, we were able to migrate our solution from Xamarin to MAUI (.net 8). After a 2 weeks fight, the app is finally working on my dev devices. Unfortunately, after sending the app to review, it gets rejected because of the following: ITMS-90338: Non-public API usage - The app references non-public symbols in [Our app name]: _SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSource, _SCDynamicStoreKeyCreateNetworkServiceEntity, _SCDynamicStoreSetNotificationKeys. 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/ From what I understand, this is because the 4 methods (_SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSourc
I've updated my mac to Sequoia (MacOS 15) beta, my iPhone to iOS 18 beta, and Xcode to Xcode 16 beta. Only then, I realized I couldn't publish app updates with Xcode beta (error in AppStore Connect). I tried using the non-beta Xcode version but got Invalid Binary during app review: ITMS-90111: Unsupported SDK or Xcode version - App submissions must use the latest Xcode and SDK Release Candidates (RC). For details on currently supported versions, visit: https://developer.apple.com/news/releases. I really need to publish updates and I can't wait for September. I can't downgrade my devices because that would require me to erase both my Mac and my iPhone (for testing), which is not something I can do. Is there any option I didn't think about? How can I publish app updates in the current situation? It really should be more explicit before updating that you can't release updates with the beta versions...
App got rejected with this reason, ITMS-91065: Missing signature Your app includes “Frameworks/FMDB.framework/FMDB”, which includes FMDB, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. If a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a signature file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a signature. For details about verifying the code signature for a third-party SDK, visit: https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks .