Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

Reply to ITMS-90338: Non-public API usage automatic refuse
I'm having the same error only on the Mac Catalyst build with no significant changes to my source code: ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in Contents/PlugIns/BookTrackWidgetsExtension.appex/Contents/MacOS/BookTrackWidgetsExtension: UIPrintPageRenderer, UISimpleTextPrintFormatter ,The app contains or inherits from non-public classes in Contents/PlugIns/BookTrackIntentHandler.appex/Contents/MacOS/BookTrackIntentHandler: UIPrintPageRenderer, UISimpleTextPrintFormatter ,The app contains or inherits from non-public classes in Contents/MacOS/Book Track: UIPrintPageRenderer, UISimpleTextPrintFormatter . 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 t
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Jun ’22
Non Consumable Titles
I'm trying to add Non-Consumable Titles to our Apple and I have been getting strange errors. Then I came across this on the Apple Forum We’re reaching out to let you know about upcoming changes to in-app purchase content hosting. In Xcode 13.3, we’ve removed the option to upload non-consumable in-app purchase assets for Apple to host. In addition, support for managing these assets in App Store Connect will be removed starting in April 2022. They suggest for us to use ODR? Is this for real? We can't use ITMSTransporter to upload new Non-Consumable Titles to our App? This is the command I been using after I create the itmsp package: /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter -m upload -f /Users/abc/Desktop/2022-06-10-13-58-27.itmsp -u xyz@abc.com -p ******** But I'm able to create Non-Consumable titles when I log into the https://appstoreconnect.apple.com/ Is Apple really expecting us to change to ODR?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
0
0
1.1k
Jun ’22
ITMS-90338: Non-public API usage for UIPrintInfo, UIPrintInteractionController in Mac Catalyst app
We have several Mac Catalyst apps that use UIPrintInfo and UIPrintInteractionController to support printing. Both of these classes are marked as available on Mac Catalyst 13.1 in the documentation and we do not receive any errors or warnings using them in our app. We have successfully uploaded to App Store Connect recently with apps that use those classes, but now are receiving error messages from App Store Connect complaining that the use of these classes is non-public API and receive the ITMS-90338 error, even though no code has changed. Is this an issue on the validation side, or are these classes no longer supported on Mac Catalyst? Thanks in advance for any help!
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
23
0
5.4k
Jun ’22
ITMS-90338: Non-public API usage
We started receiving this error a few days ago when it appeared to be a wide spread problem on Apple's end. https://developer.apple.com/forums/thread/127678?answerId=715975022#715975022 Although it is supposedly resolved, I am still getting this error. I have incremented build and version numbers along with tweaking code. Also, the build agent is running macOS 12.4 and Xcode 13.4.1. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app references non-public selectors in Align-Dev: isActivated. 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/ The only
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
4
0
3.0k
Jun ’22
UIMarkupTextPrintFormatter - Non-public API?
I recently had a build go into the system for Test Flight distribution and got the automated message: ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in Contents/MacOS/: UIMarkupTextPrintFormatter. I've been using UIMarkupTextPrintFormatter for a long time, and it appears to be a very-public API. I don't even see it as being marked obsolete/deprecated. Is anyone else getting this message? Is this just a goof on Apple's part, or will I need to find some alternative to UIMarkupTextPrintFormatter?
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
909
Jun ’22
Xcode Cloud - Invalid Code Signing Entitlements
After building my app with Jenkins for 3 years without any problems, I'm now trying to build with Xcode Cloud and I'm getting the following error: ITMS-90045: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.game-center I deleted the capability from the Xcode and the info.plist file, yet I'm still getting the error. Any ideas?
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
2
0
1.9k
Jun ’22
Reply to com.apple.developer.game-center not supported ios
I have the same issue. [Transporter Error Output]: ERROR ITMS-90045: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.game-center' in 'Payload/***********.app/***********' is not supported. I used an identical Fastlane configuration for an app generated yesterday and it deployed to TestFlight and App Store perfectly.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Jun ’22
ERROR ITMS-90189: "Redundant Binary Upload.", but the binary is not showing up in TestFlight.
Hi all, I am encountering a problem where I am attempting to upload an IPA to TestFlight using fastlane. In my first attempt, I received no errors. However, even after hours of waiting, there is still no binary on TestFlight for that version and build number. In my second and following attempts, I get this error: ERROR ITMS-90189: Redundant Binary Upload. You've already uploaded a build with build number '18445' for version number '3.66.0'. Make sure you increment the build string before you upload your app to App Store Connect. Learn more in Xcode Help (http://help.apple.com/xcode/mac/current/#/devba7f53ad4). To clarify again, if I go into TestFlight, there is no version 3.66.0. The build number is supposed to automatically increment, as it does previously. So there are multiple problems here for me. Binary not showing up in TestFlight TestFlight thinks the binary is there, so I'm not able to automatically increment build number.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
1
0
1.7k
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
I got similar issue, I just do some mirror changes in my code, and I could submit it successful before 2 days. ITMS-90338: Non-public API usage - The app references non-public selectors in XXXX: debug:, estimatedProgress, evaluateScript:, imageForKey:, info:, initWithFrame:configuration:, isMainFrame, navigationDelegate, navigationType, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, parentFrame, setBundle:, setImage:forKey:, setNavigationDelegate:, setProcessPool:, setSelectionGranularity:, targetFrame, userContentController, warn:, websiteDataStore. 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.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same issue ITMS-90338: Non-public API usage - The app references non-public selectors in tct-34: addParticipants:, determineAppInstallationAttributionWithCompletionHandler:, dismiss:, filterButtonAction:, fontWeight, initWithFrame:configuration:, isMainFrame, lookupAdConversionDetails:, navigationDelegate, relativeSize, setNavigationDelegate:, spanArray, spanArray_Count, underline, userContentController.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
ITMS-90338: Non-public API usage - The app references non-public selectors in FFS_NewAPPStore: currentSession, initWithFrame:configuration:, isMainFrame, navigationDelegate, setNavigationDelegate:, setProcessPool:, targetFrame, userContentController. 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
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
ITMS-90338: Non-public API usage - The app references non-public selectors in NHCSXH: authenticationDidCompleteWithError:, estimatedProgress, identityToken, initWithFrame:configuration:, isMainFrame, navigationType, onSuccess:, setColor:animated:, setNavigationDelegate:, setProcessPool:, targetFrame, toggleEditing:, userContentController, websiteDataStore same error
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Jun ’22