“ITMS-90338”

Hello, I'm getting the title's error for the first time. I'm using expo for my React Native build and I have only added these libraries to my build: react-native-md5: ^1.0.0, moment-timezone: ^0.5.43 How are these changes connected to the error? These are my system specs: XCode version 14.2 (14C18) MacOS version 12.6.7 (21G651)

What I Whant I'm making a component. This component is used to display a list of tags. I want a context menu to pop up on the tag when the user long-presses it. Like this: What I Got Here is My Code VStack(alignment: .leading) { ForEach(groupedItems, id: .self) { itms in HStack { ForEach(itms, id: .self) { tag in Text(tag.title ?? ) .font(.callout) .padding() .frame(height: 24.0) .frame(alignment: .center) .cornerRadius(100) .contextMenu { Button { deleteTheTag(tag) } label: { Label(Delete, systemImage: trash) } } } } } } I tried several methods, but all failed. How should I modify my code?

Uploading an IPA using /usr/local/itms/bin/iTMSTransporter -m upload -assetFile -u -p -v informational -asc_provider method, if an application successfully uploads for the first time and the version of the IPA+1, it will be rejected upon upload. The reason for rejection is: Package Summary: 1 package(s) were not uploaded because they had problems: /Users/****/Desktop/3/app.ipa - Error Messages: Upload is not in processing state, please try again. state: class Build { type: builds id: 873e65d2-7cb2-4acf-868b-7f95c6893784 attributes: class BuildAttributes { version: 1 uploadedDate: 2023-08-01T23:48:33.661-07:00 expirationDate: null expired: null minOsVersion: null lsMinimumSystemVersion: null computedMinMacOsVersion: null iconAssetToken: null

Getting the following incorrect error when uploading to App Store Connect. I've tried with Xcode and Transporter. The APIs are not being referenced anywhere in my project. There was a similar issue to this on the forum a couple weeks ago and it sounded like Apple resolved it but I am just now seeing this happen. Message: ITMS-90338: Non-public API usage - The app references non-public symbols in APP_NAME: _CMTimebaseCopyMasterTimebase, _CMTimebaseCreateWithMasterClock, _CMTimebaseCreateWithMasterTimebase. 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.

Got this message from email when submitting an app to test flight around GMT+7 2pm. The app references non-public symbols in Frameworks/AmazonIVSPlayer.framework/AmazonIVSPlayer: _CMTimebaseCreateWithMasterClock. 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/

Hi, Our project utilizes push notifications via OneSignal SDK. Everything looks correct and conforms with the documentation: The Push Notifications capability is enabled in XCode. The entitlements do contain the aps-environment key with the production value. I unpacked the resulting IPA and explored embedded.mobileprovision file - it does contain the aps-environment key with the production value in the Entitlements section too. The App ID and provision profiles used do include the Push Notification capability. So there's literally nothing to fix. Despite of that, when uploading the IPA to AppStore Connect, we receive an email with the warning ITMS-90078: Missing Push Notification Entitlement... that says there's no aps-environment entry. Moreover, the OneSignal dashboard indicates Missing Push Capabilities for all the iOS devices that run our application. Consequently, the push messages are not received. What could be wrong with the IPA and where to look at? Thanks in advance!

ITMS-90512: Invalid sdk value - The value provided for the sdk portion of LC_VERSION_MIN_IPHONEOS in Runner.app/Frameworks/WebEngage.framework/WebEngage is 17.0 which is greater than the maximum allowed value of 16.5. I'm using latest stable Xcode. Version 14.3.1. How can I fix this issue?

Questions When I installed the Firebase DynamicLinks Unity SDK and uploaded it to TestFlight, I have received an email from AppleStoreConnect stating ITMS-90078: Missing Push Notification Entitlement. Q1. is there any chance that leaving this situation unresolved will lead to rejection or suspension of distribution at the time of AppStore release? Q2. if anyone knows of a solution to this problem, please let me know. Background We are developing with Unity, a game development engine, outputting an Xcode project, and uploading it to TestFlight from Xcode. We have enabled Push Notification in the Capabilities setting of AppID, but we do not use this feature in our app, and we do not use a certificate for Push Notification. The same AppID setting did not send the same email until now, but when the Unity SDK for Firebase Dynamic Links was installed, the above email started to arrive. We believe that it is difficult to solve the problem at present, because there is a report on the Github issue of the SDK

I'm dealing with a problem uploading our release binaries that is completely perplexing. If I use the ITMS Transporter desktop app to upload my IPA, everything works fine. If I use the ITMS Transporter command line interface (which i'm calling from inside the desktop app's directory /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter -m upload...) to upload my IPA, I get the following error ERROR ITMS-90529: Invalid package. Applications built with sdk 9.0 or later must be packaged as proper IPA files. No idea why this error is coming up. I can also use altool to upload my binaries successfully. The issue is altool is being deprecated and I need to be able to use the ITMS command line interface as part of some deployment scripts we have. Please help!

I regularly come across Mac developers who have an app in the Mac App Store but are unable to submit it to TestFlight. This post explains a common cause of that problem. If you have any questions or comments about this, start a new thread and tag it with Provisioning Profiles and TestFlight so that I see it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com TestFlight, Provisioning Profiles, and the Mac App Store A provisioning profile authorises a device to run your app. For historical reasons, not all Mac apps need a provisioning profile. A Mac app only needs a profile if it uses a restricted entitlement, that is, an entitlement that must be authorised by a profile. For more background on this, see TN3125 Inside Code Signing: Provisioning Profiles and, specifically, its Entitlements on macOS section. IMPORTANT Your Mac App Store apps must be signed with the App Sandbox Entitlement, but that entitlement is unrestricted. This means that many M