ITMS-90158

HI! We received this message from technical support Multiline ITMS-90338: Non-public API usage - The app references non-public selectors in SMMplanner: _isKeyDown, _modifiedInput, _modifierFlags. 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/ BlockQuote but problem is that _isKeyDown, _modifiedInput, _modifierFlags are is internal react-native library methods! And we can't do nothing to fix it. So how can we solve this problem?

Hi team,When uploading the ipa via transporter command line utility, the following message is returned. We are re-signing manually and curiously, the errors only occurs for app extensions and not the main app. ERROR ITMS-90164: Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '''TeamId.ExtBundleId''' for the key '''application-identifier''' in '''Payload/MyApp.app/PlugIns/MyAppExtension/MyAppExtension'''. We are signing manually and our app entitlements are as such <plist version=1.0> <dict> <key>application-identifier</key> <string>TeamId.ExtBundleId</string> <key>aps-environment</key> <string>production</string> <key>beta-reports-active</key> <true/> <key>com.apple.developer.team-identifier</key> <string>TeamId<

ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/ documentation/uikit/uiwebview). how it's possible though i'm not use it anywhere whether it is in main directory or pod

ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/ documentation/uikit/uiwebview). actually i didn't use deprecated API since i face this issue and app automatically removed from TestFlight kindly do needy thanks.

Dear Developer, We identified one or more issues with a recent delivery for your app Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public symbols in Loupe: _CGImageGetImageSource. 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/ Best regards, The App Store Team There are two problems, one is that our release/production build is succeeding and uploading to TestFlight. The other problem is we do not understand what the issue is even when reading your automatic message. How can we debug this ? How can we identify the source of the problem ? Do you have a

ITMS-90338: Non-public API usage - The app references non-public selectors in SMMplanner: _isKeyDown, _modifiedInput, _modifierFlags. 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/

I want to create a hyperlink for OTA installation of my iOS app on the Azure DevOps wiki page, has anyone tried it? I have tried using html tag, but when I click it, it only refreshes the wiki page. This is the link example using tag. My App I have also tried using markdown link, but it seems it doesn’t recognize itms-services syntax, this is the link example [My App](itms-services://?action=download-manifest&url=https://my.app.com/install.plist)

i got ITMS-90109 before, and areally fix it. but when i update a new build for my new version, the (Add to review) button no work?

I get the following error in Xcode Cloud when attempting to prepare a build for App Store: ITMS-90334: Invalid Code Signature Identifier. The identifier SwiftCharts-555549449cfa473253483215b74c174849d2ec9c in your code signature for SwiftCharts must match its Bundle Identifier SwiftCharts. This is an iOS app and Swift Charts is swift package dependency which the app depends on. Since it is a dynamic library, it is included via the Embed & Sign option. This was reported on SO by another user. They worked around it by making changes to the source package, I believe. That workaround may be difficult in my case as I do not control the source package. It's a 3rd party dependency that I'd prefer not to maintain a fork of. Any ideas of why Xcode cloud is hitting this issue or any other workarounds? I've confirmed via a codesign check that the Identifier is resolving to that special hash when doing this from Xcode Cloud. It does not have that hash when I attempt to build/archive/upload locally. $ codesig

Has anyone successfully used Xcode Cloud with App Clips. Every time I do a build I get an error from App Store Connect for Missing Entitlement. ITMS-90876: Missing entitlement - This app contains an app clip. The entitlement 'com.apple.developer.associated-appclip-app-identifiers' should be present and include the value of the app clip's application identifier. Xcode adds this automatically and an archive direct from Xcode works successfully. It seems that Xcode cloud is not automatically adding this entitlement which causes an error on submission.

We are creating a universal build of our application for the Mac App Store by merging separate x86_64 and arm64 bundles using a script. Codesign verification fails for some dylibs if they are signed after merging: % lipo -create x86_64/test.dylib arm64/test.dylib -o universal/test.dylib % codesign -s *** -f --timestamp universal/test.dylib % codesign --verify --verbose=2 universal/test.dylib test.dylib: invalid Info.plist (plist or signature have been modified) It seems verification fails for only those dylibs that have an Info.plist embedded in them. We were able to work around this issue by signing the individual dylibs before merging, but now AppStore verification is failing with the following error: ITMS-90336: Mismatched Embedded Info.plist: The executable 'test.dylib' has mismatched embedded Info.plists. This could be due to the use of 3rd party build tools. Does this mean that the __info_plist section in all the slices in the universal binary should be exactly the same (bitwise)? Some of these

I am trying to upload a new build of my app from the new Xcode 14.1 RC but it keeps failing with the below error: ITMS-90428: Invalid Swift Support - The files libswift_Concurrency.dylib don’t match /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib. Make sure the files are correct, rebuild your app, and resubmit it. Don’t apply post-processing to /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib. My bundle contains a watchOS 4.3 app which I thought might have been an issue, so I tried increasing it to watchOS 7.0 but still got the error. Bitcode is disabled for all targets. I don't have post-processing enabled either.

Hello, The problem is we do not understand what the issue is even when reading your automatic message. Detail, before updating to version 14 it worked perfectly, so much so that it was deployed to the store. Today it works perfectly on the emulator and on the device, by xcode. How can we debug this ? How can we identify the source of the problem ? Do you have any idea of what the problem is ? Xcode: 14.0.1 macOS: Monterey Pro Chip M1 React Native: 0.69.5