Search results for

ITMS-90158

1,685 results found

Post

Replies

Boosts

Views

Activity

ITMS-90076: Potential Loss of Keychain Access
We have transferred our app from App Store Connect account to another. Transfer process was smooth and we we were able to move our app to new App Store account While uploading the new build for our app using the new account we received the below email. Can someone shed some lights on this and how can we make user to not to logout. ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['94B63VZT32.com.prasthana.tenmates'] and the new version of software being submitted has an application-identifier of ['G3M3U47GBZ.com.prasthana.tenmates']. This will result in a loss of keychain access.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
1
0
662
Sep ’24
ITMS-91093
Hi, I'm encountering an issue when trying to upload a build to App Store Connect. I'm receiving an 'Invalid Binary' error with the following message: ITMS-91093: Invalid Binary - The app contains a binary [path to a zip file] that cannot be processed. The error appears to be linked to a folder containing zip files that is referenced in the 'Build Phases' under the 'Copy Bundle Resources' section. Everything was working fine until a few days ago.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
0
0
591
Sep ’24
Icon Fonts failing review submission with ITMS-90853: Invalid font
Hello. Icon fonts such as Font Awesome 6 and react-native-vector-icons are being rejected submission with the automated Invalid Binary error. ITMS-90853: Invalid font - There was an error validating the font named 'FontAwesome6Free-Solid' at 'private-app-name/FontAwesome6_Solid.ttf'. ‘glyf’ table instructions. These fonts have previously worked over the course of the last 3 years without issue and just stopped working on Monday. GitHub is filled with related issues and bug reports. This is likely affecting thousands of apps.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
2
0
952
Sep ’24
Reply to itmstransporter cannot install on Linux aarch64
Indeed, I found the directory /usr/local/itms was created, but command seems not working: [2024-09-10 07:08:52 UTC] DEBUG: Setting System property: DataCenters = contentdelivery02.itunes.apple.com,contentdelivery01.itunes.apple.com [2024-09-10 07:08:52 UTC] DEBUG: Setting System property: DataCenters.host = contentdelivery02.itunes.apple.com [2024-09-10 07:08:52 UTC] DEBUG: Setting System property: DataCenters.setBy = Defaults.properties [2024-09-10 07:08:54 UTC] INFO: Configuring logging... [2024-09-10 07:08:54 UTC] INFO: Logging level set to eXtreme [2024-09-10 07:08:54 UTC] ERROR: unsatisfied requirement: com.apple.amp.mudhorn.mudhorn-client-x86_64-unknown-linux-musl [2024-09-10 07:08:54 UTC] ERROR: (&(osgi.native.osname~=Linux)(osgi.native.processor~=x86-64)) [2024-09-10 07:08:54 UTC] ERROR: unsatisfied requirement: com.apple.transporter.vbtx-rs-universal-apple-darwin [2024-09-10 07:08:54 UTC] ERROR: (&(osgi.native.osname~=MacOSX)(|(osgi.native.processor~=x86-64)(osgi.native.proc
Topic: Developer Tools & Services SubTopic: Instruments
Sep ’24
App Store Connect invalidating binary during App Review - built with Xcode Cloud / Xcode 16 RC
I archived and uploaded a build with Xcode 16 RC earlier today since it wasn't available in Xcode Cloud at that moment. The upload was successful. Since then, Xcode Cloud was updated with Xcode 16 RC and I can build and deploy to TestFlight and App Store Connect that way too. Now, upon submitting my app to App Review, the binary is being rejected as invalid due to unsupported version of Xcode. Rejections Sept 9th at 11:28 PM Central and Sept 10th 12:37 AM. Here is the error message I received via email: 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. Upon visiting the site, you can see a developer news article stating that App Review is now accepting builds created from Xcode 16 RC. I assume this is just the system going through upgrades and the whole system isn't updated yet. Is anyone else having issues submitting Xcode 16 RC builds
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
10
0
2k
Sep ’24
Contact Prodvider Extension key 'com.apple.contact.provider.extension' not accepting in Testflight submission
ERROR ITMS-90349: Invalid Info.plist value. The value of the EXExtensionPointldentifier key, com.apple.contact.provider.extension, in the Info.plist of MainApp.app/Extensions/ContactProviderExtension.appex is invalid. We were working on new iOS18 Contacts Provider extension and when try to test the feature in testflight we were unable to submit the build and getting the above error. The extensionPointldentifier 'com.apple.contact.provider.extension' was auto generated by xcode and apple doc mentioned the same value to use for Contacts Provider extension support. But it is not accepting in testflight. https://developer.apple.com/documentation/contactprovider/contactproviderextension Any help will be appreciated.
Topic: UI Frameworks SubTopic: General Tags:
0
0
695
Aug ’24
Reply to Why can't I have INPlayMediaIntent in 2 extensions?
Oh yes, I used that Car Play Music Sample to add CarPlay to my app and it seems to work good but now I need to make sure Siri works with CarPlay and the main app, the watch, HomePod and everything else. I'm just running into conflicts with INPlayMediaIntent plus I'm working on a Radio app so when a user says Hey Siri, play Beatles Radio the phone tries to play Beatles in my music library instead of my app. I have 40 other radio stations with the word radio in the name, so I'm dealing with that. I'm getting lots of other errors when I try to upload to appstoreconnect, but will deal with them later: ITMS-90626: Invalid Siri Support - '' is not a supported intent type Though you are not required to fix the following issues, we wanted to make you aware of them: ITMS-90626: Invalid Siri Support - No example phrase was provided for INSendMessageIntent in the 'pt-br' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabu
Topic: Media Technologies SubTopic: Audio
Aug ’24
xcode cloud build failed ITMS-90055: This bundle is invalid
Environment info Local machine: macos xcode 16 beta macOS Sequoia beta xcode cloud: Xcode latest release version (15.4). MacOS latest version I checked my project bundle identifier several times, it absolutly match to Apple Store connect. IIs failed occurred when workflow archive - distribution select testfight. If I select None in distribution, it Build success in Xcode cloud. Ps: I cannot archive from local machine, it shows Xcode version should be released version. Anyone meet the same problem? --- failed notification email attached below --- We noticed one or more issues with a recent delivery for the following app: WGesture Watch App Version 1.0 Build 8 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90055: This bundle is invalid - The bundle identifier cannot be changed from the current value, 'com.war.WGesture.watchkitapp'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
2
0
810
Aug ’24
App document icon in spotlight on mac
Hello. I'm adding my mac app contents to spotlight index. I have created a dedicated exported document type which Finder also recognises and shows documents with my extension artcl with correct icon I provide with the app. But it does not happen in Spotlight - it shows my documents with default icon. I create items for Spotligh index as follows: let myType = UTType(filenameExtension: artcl)! var searchableItems: [CSSearchableItem] = [] for itm in items.reversed() { let attributeSet = CSSearchableItemAttributeSet(contentType: myType) attributeSet.title = item.title attributeSet.contentDescription = item.desc attributeSet.displayName = item.name attributeSet.keywords = [ item.title ] attributeSet.comment = item.title + + item.desc attributeSet.contentType = com.devaikin.spottest.artcl let id = artcl. + item.title + . + item.name let indexItem = CSSearchableItem(uniqueIdentifier: id, domainIdentifier: artcl, attributeSet: attributeSet) searchableItems.append(indexItem) let defaultIndex = CSSearchableI
Topic: App & System Services SubTopic: General Tags:
0
0
670
Aug ’24
Submitting 2 apps with the same framework => 1 passes, 1 has ITMS-91065 error
Hi, I manage apps for several clients. I have 2 apps for 2 different clients in which I use OneSignal version 5.1.5 (https://github.com/OneSignal/OneSignal-XCFramework). The OneSignal part of these 2 applications are configured identically. For both applications I can Build the project Create an archive of the project Send the archive to TestFlight Install the TestFlight version on an iPhone Launch the app on the iPhone For the 1st application I can submit to AppStore it without any problem. For the 2nd application when I submit to AppStore it I have the error ITMS-91065 almost immediately in return by email. ITMS-91065: Missing signature - Your app includes “Frameworks/OneSignalCore.framework/OneSignalCore”, which includes OneSignalCore, 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 t
Topic: App Store Distribution & Marketing SubTopic: General Tags:
1
0
944
Aug ’24
Reply to <compiler-generated> Error shows fatal crash in firebase crashlytics...but the app does not crash for the user
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
Topic: App & System Services SubTopic: General Tags:
Jul ’24
How to resolve "ITMS-90129: The bundle uses a bundle name or display name that is already taken" for new builds of the same app
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
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
1
0
1.2k
Jul ’24
Can't open app on TestFlight
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.
Topic: App Store Distribution & Marketing SubTopic: TestFlight
1
0
462
Jul ’24