Search results for

“ITMS-90338”

1,703 results found

Post

Replies

Boosts

Views

Activity

Reply to ITMS-90338: Non-public API usage automatic refuse
same here, this didn't start for us until today - no library/pod changes and all of the sudden apple is complaining about methods/selectors that are being used by pods we've used for years and successfully submitted app review ITMS-90338: Non-public API usage - The app references non-public selectors in XXXXXXX: estimatedProgress, initWithFrame:configuration:, isMainFrame, navigationType, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, setNavigationDelegate:, setProcessPool:, socket:didAcceptNewSocket:, socket:didConnectToHost:port:, socket:didConnectToUrl:, socket:didReadData:withTag:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidDisconnect:withError:, socketDidSecure:, targetFrame, userContentController, websiteDataStore. If method names in
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same here. I even tried with a git reset head to make sure it was exactly the same version. I'm using the latest version of capacitor, nothing else. ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/Capacitor.framework/Capacitor: applicationNameForUserAgent, initWithFrame:configuration:, isMainFrame, setNavigationDelegate:, targetFrame.
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Hi, I have the same error now: ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/JXWebViewController.framework/JXWebViewController: isMainFrame, setNavigationDelegate:, targetFrame. 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 Any solution?
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Hi, I have the same error. I put here: https://github.com/swordray/JXWebViewController/issues/1 And the message is: ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/JXWebViewController.framework/JXWebViewController: isMainFrame, setNavigationDelegate:, targetFrame. 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
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same here, an app that has been releasing updates without issues for months. Even 2 days ago, a testflight version successfully uploaded, but today it just failed after simple (non native) changes. TMS-90338: Non-public API usage - The app references non-public selectors in zinspector3: estimatedProgress, initWithFrame:configuration:, isMainFrame, isPassthrough, navigationType, onSuccess:, removeValuesForKeys:completion:, setNavigationDelegate:, setProcessPool:, targetFrame, userContentController, websiteDataStore. Did apple turn on a setting that bans all these out of the blue? Or did someone add a not condition in their code and now everything is flagged?
Jun ’22
Reply to ITMS-90876: Missing entitlement
The com.apple.developer.parent-application-identifiers entitlements are both added automatically to the app clip target on creation. Xcode doesn't seem to add the corresponding com.apple.developer.associated-appclip-app-identifiers entitlement to the parent app target. I added it (manually) to the parent app's entitlements file, with the value $(AppIdentifierPrefix)com.myproject.Clip, and it seems to work. Didn't get another ITMS-90876 error email from App Store Connect after submitting.
Topic: Code Signing SubTopic: Entitlements Tags:
May ’22
Mac App Store url problem on Mac M1
Hello, I have an iOS application which has a rate us button. This button redirects to Write review section on the app's App Store. It is working great on both iPhone and iPad devices. The problem is on MacBook M1 - it is working, but once the App Store app for review is opened, my iOS app crashes :( UIApplication.shared.open(URL(string: itms-apps://itunes.apple.com/us/app/app-name/id*****?action=write-review)!) Any ideas on how it can be fixed? Thanks!
11
0
3.7k
May ’22
ITMS-90053, ITMS-90055, ITMS-90345 Error when trying to archive a duplicated app
Hi, I am creating a workflow in Xcode Cloud for a duplicated react-native application. I have changed the bundle identifier and created a new application in App Center with the same bundle identifier. in cloud when I am trying to proceed with the step Archive-IOS it throws following errors, but those are not thrown in Build-IOS step. Please provide me some suggestions. Error details: ITMS-90053: This bundle is invalid - The bundle identifier is already in use by a different software package. ITMS-90055: This bundle is invalid - The bundle identifier cannot be changed from the current value, '(duplicated.app.build.identifier)'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect. ITMS-90345: Metadata/Info.plist Mismatch - The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in (Old App Name) [Payload/(oldappName)].
2
0
2.2k
May ’22
Using XCode 13.3.1 and SDK 15 but build won't load through Transporter App and error email says : ITMS-90725: SDK Version Issue - This app was built with the iOS 14.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK
Hi, I am trying to upload a mobile game I created for iOS app store for beta testing with friends and family through testflight. I have especially purchased a MacBook Pro running XCode 13.3.1 and Monterey 12.3.1 and an iPhone running Software version 15.4.1 to this end. My XCode deployment target is set to iOS 15.4 and my Unreal Engine 5.01 minimum iOS version in packaging is set to 15. As far as I can tell everything is set to be as up to date version wise as possible, yet every time I try uploading the packaged game through transporter app the build won't show up in App Store Connect and I get an error email from the development team saying : ITMS-90725: SDK Version Issue - This app was built with the iOS 14.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Now I've emailed the team and their response was to version up and try again and look for the error in the email. So I did that and got the exact same error and no build ava
4
0
6.3k
May ’22
agvtool doesn't update extension Marketing Version
We have a bit of a complicated build process and need to build the Widget outside of our main app and repackage since we are using a cross platform framework. I tried scripting out updating my Widget's Marketing Version but agvtool won't update the MARKETING_VERSION in the project.pbxproj file. Therefore, we end up getting these emails from Apple: ITMS-90473: CFBundleShortVersionString Mismatch - The CFBundleShortVersionString value ‘1.2.2’ of extension ‘MyiOSApp.app/PlugIns/widgetExtension.appex' does not match the CFBundleShortVersionString value ‘1.2.3' of its containing iOS application ‘MyiOSApp.app'. I run this and it says it's updating in the Widget plist (but not the project.pbxproj) so when I build with xcode via command line it doesn't update and when we submit to the App Store we get the above message from Apple: /usr/bin/agvtool new-marketing-version $(/usr/libexec/PlistBuddy -c Print :CFBundleShortVersionString ../My.Crossplatform.App/My.Crossplatform.App.iOS/Info.plist) Setting CFBundleS
6
0
7.1k
Apr ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
same here, this didn't start for us until today - no library/pod changes and all of the sudden apple is complaining about methods/selectors that are being used by pods we've used for years and successfully submitted app review ITMS-90338: Non-public API usage - The app references non-public selectors in XXXXXXX: estimatedProgress, initWithFrame:configuration:, isMainFrame, navigationType, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, setNavigationDelegate:, setProcessPool:, socket:didAcceptNewSocket:, socket:didConnectToHost:port:, socket:didConnectToUrl:, socket:didReadData:withTag:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidDisconnect:withError:, socketDidSecure:, targetFrame, userContentController, websiteDataStore. If method names in
Replies
Boosts
Views
Activity
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same here. I even tried with a git reset head to make sure it was exactly the same version. I'm using the latest version of capacitor, nothing else. ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/Capacitor.framework/Capacitor: applicationNameForUserAgent, initWithFrame:configuration:, isMainFrame, setNavigationDelegate:, targetFrame.
Replies
Boosts
Views
Activity
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Hi, I have the same error now: ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/JXWebViewController.framework/JXWebViewController: isMainFrame, setNavigationDelegate:, targetFrame. 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 Any solution?
Replies
Boosts
Views
Activity
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Hi, I have the same error. I put here: https://github.com/swordray/JXWebViewController/issues/1 And the message is: ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/JXWebViewController.framework/JXWebViewController: isMainFrame, setNavigationDelegate:, targetFrame. 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
Replies
Boosts
Views
Activity
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same here, an app that has been releasing updates without issues for months. Even 2 days ago, a testflight version successfully uploaded, but today it just failed after simple (non native) changes. TMS-90338: Non-public API usage - The app references non-public selectors in zinspector3: estimatedProgress, initWithFrame:configuration:, isMainFrame, isPassthrough, navigationType, onSuccess:, removeValuesForKeys:completion:, setNavigationDelegate:, setProcessPool:, targetFrame, userContentController, websiteDataStore. Did apple turn on a setting that bans all these out of the blue? Or did someone add a not condition in their code and now everything is flagged?
Replies
Boosts
Views
Activity
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same to me... ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/Capacitor.framework/Capacitor: applicationNameForUserAgent, initWithFrame:configuration:, isMainFrame, setNavigationDelegate:, targetFrame. Any solution for this?? Thx!
Replies
Boosts
Views
Activity
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same to me... ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/Capacitor.framework/Capacitor: applicationNameForUserAgent, initWithFrame:configuration:, isMainFrame, setNavigationDelegate:, targetFrame.
Replies
Boosts
Views
Activity
Jun ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same issue using Flutter deployment, got ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/webview_flutter.framework/webview_flutter: initWithFrame:configuration:, isMainFrame, setNavigationDelegate:, userContentController. Tried to deploy to TestFlight but was unable to. Hopefully this gets resolved.
Replies
Boosts
Views
Activity
Jun ’22
Reply to ITMS-90876: Missing entitlement
The com.apple.developer.parent-application-identifiers entitlements are both added automatically to the app clip target on creation. Xcode doesn't seem to add the corresponding com.apple.developer.associated-appclip-app-identifiers entitlement to the parent app target. I added it (manually) to the parent app's entitlements file, with the value $(AppIdentifierPrefix)com.myproject.Clip, and it seems to work. Didn't get another ITMS-90876 error email from App Store Connect after submitting.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
May ’22
Mac App Store url problem on Mac M1
Hello, I have an iOS application which has a rate us button. This button redirects to Write review section on the app's App Store. It is working great on both iPhone and iPad devices. The problem is on MacBook M1 - it is working, but once the App Store app for review is opened, my iOS app crashes :( UIApplication.shared.open(URL(string: itms-apps://itunes.apple.com/us/app/app-name/id*****?action=write-review)!) Any ideas on how it can be fixed? Thanks!
Replies
11
Boosts
0
Views
3.7k
Activity
May ’22
ITMS-90053, ITMS-90055, ITMS-90345 Error when trying to archive a duplicated app
Hi, I am creating a workflow in Xcode Cloud for a duplicated react-native application. I have changed the bundle identifier and created a new application in App Center with the same bundle identifier. in cloud when I am trying to proceed with the step Archive-IOS it throws following errors, but those are not thrown in Build-IOS step. Please provide me some suggestions. Error details: ITMS-90053: This bundle is invalid - The bundle identifier is already in use by a different software package. ITMS-90055: This bundle is invalid - The bundle identifier cannot be changed from the current value, '(duplicated.app.build.identifier)'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect. ITMS-90345: Metadata/Info.plist Mismatch - The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in (Old App Name) [Payload/(oldappName)].
Replies
2
Boosts
0
Views
2.2k
Activity
May ’22
Using XCode 13.3.1 and SDK 15 but build won't load through Transporter App and error email says : ITMS-90725: SDK Version Issue - This app was built with the iOS 14.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK
Hi, I am trying to upload a mobile game I created for iOS app store for beta testing with friends and family through testflight. I have especially purchased a MacBook Pro running XCode 13.3.1 and Monterey 12.3.1 and an iPhone running Software version 15.4.1 to this end. My XCode deployment target is set to iOS 15.4 and my Unreal Engine 5.01 minimum iOS version in packaging is set to 15. As far as I can tell everything is set to be as up to date version wise as possible, yet every time I try uploading the packaged game through transporter app the build won't show up in App Store Connect and I get an error email from the development team saying : ITMS-90725: SDK Version Issue - This app was built with the iOS 14.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Now I've emailed the team and their response was to version up and try again and look for the error in the email. So I did that and got the exact same error and no build ava
Replies
4
Boosts
0
Views
6.3k
Activity
May ’22
In-App Purchases New Titles
When I try to create a new title for my app i'm getting a ERROR ITMS-2000: Verison '3.11.3', Locale 'en-US': title cannot be edited in the current state Does anyone know where I can see if the Create template changed for Apple API for Apps?
Replies
0
Boosts
0
Views
366
Activity
May ’22
Error with uploading something using itmstransporter
When I try to create a new title for my app i'm getting a ERROR ITMS-2000: Verison '3.11.3', Locale 'en-US': title cannot be edited in the current state Mac that I'm using is currently on 10.15.7. Transporter APP version is on 1.1.1
Replies
0
Boosts
0
Views
491
Activity
May ’22
agvtool doesn't update extension Marketing Version
We have a bit of a complicated build process and need to build the Widget outside of our main app and repackage since we are using a cross platform framework. I tried scripting out updating my Widget's Marketing Version but agvtool won't update the MARKETING_VERSION in the project.pbxproj file. Therefore, we end up getting these emails from Apple: ITMS-90473: CFBundleShortVersionString Mismatch - The CFBundleShortVersionString value ‘1.2.2’ of extension ‘MyiOSApp.app/PlugIns/widgetExtension.appex' does not match the CFBundleShortVersionString value ‘1.2.3' of its containing iOS application ‘MyiOSApp.app'. I run this and it says it's updating in the Widget plist (but not the project.pbxproj) so when I build with xcode via command line it doesn't update and when we submit to the App Store we get the above message from Apple: /usr/bin/agvtool new-marketing-version $(/usr/libexec/PlistBuddy -c Print :CFBundleShortVersionString ../My.Crossplatform.App/My.Crossplatform.App.iOS/Info.plist) Setting CFBundleS
Replies
6
Boosts
0
Views
7.1k
Activity
Apr ’22