ITMS-90158

I have recently added some Swift files to my Objective C project that I had been successfully publishing to the AppStore. I'm able to debug on my devices and simulators but when submitting to AppStoreConnect I get the following email: Dear Developer, We identified one or more issues with a recent delivery for your app, ...... . Please correct the following issues, then upload again. ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Best regards, The App Store Team From the internet I gather the following build settings are required for the project but that doesn't seem to help my case: 1. Defines Module -> YES 2. Always embed Swift Standard libraries -> YES To reproduce the problem, do the following: Create new Objective C project in XCode Add a single Swift file and choose YES when prompted to make the bridging header Set Defines Module and Always embed Swift Standard libraries to YES in buil

ITMS-90334: Invalid Code Signature Identifier - The identifier 'bundle id followed by 30 random characters' in your code signature for 'bundle id' must match its Bundle Identifier 'bundle id' Currently, any app I’ve tried is getting this error when submitting from the app. I’ve got all the places where you put the name, the sku, and bundle id set with the same value (copy/paste), and I’ve tried different variations, but now that long string of random characters is appended and I can’t use TestFlight. Maybe because this is a beta iPad OS? Been on a beta for what seems like forever. It’s worked in the past. Great. Totally innocuous post that has something that is not permitted. Be nice if you TELL me what’s NOT PERMITTED!

I found several services that allow you to distribute applications to users(ios). diawi appsonair deployninja unicornlab but I think they all use Apple services in their work. this is from the documentation Diawi: How wireless app installation works on iOS Over-the-air installation of apps on iOS is based on tools and features provided officially by Apple: itms-service and a valid manifest file providing information on the app. but if apple services do not work in this country - how can I install the application? or is it not possible? maybe Enterprise account can help me with this? or is it not possible?

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

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.

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?

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?

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