aws-sdk-ios
aws-sdk-ios copied to clipboard
aws-amplify
The app references non-public selectors > AWSAuthCore: reloadSession
Upgraded to Xcode 14 and started getting this validation error when submitting to the App Store:
"The app references non-public selectors in Payload/
Is this a known issue to the AWS team or perhaps a bug Apple needs to fix?
I've experienced same warning message, titled with "App Store Connect Operation Error".
Note: in my case, there was no problem for TestFlight distribution.
Same, no issue submitting to test flight but I have not tried submitting to the App Store yet.
Thanks for opening this issue. Our team will investigate and provide an update.
Hello, We are aware of this issue and currently looking into it. We'd encourage to post this on Apple Developer forums as well while we investigate this. In case this is a blocker for you, please let us know. Similar thread : https://developer.apple.com/forums/thread/713574
Same issue (with a different selector) on my side since I updated to Xcode 14 : The app references non-public selectors in Payload/app_name.app/app_name: authenticationDidCompleteWithError:
The app references non-public selectors in Payload/Frameworks/AWSAuthCore.framework/AWSAuthCore: reloadSession. I got this issue in Xcode 14.0.1 while uploading my app to the App Store.
@thisisabhash I also have this issue; for me, this build doesn't display on Testflight. Just because testflight doesn't show builds with warnings in my case. Strange behavior.
I got 2 warnings after upgraded to Xcode 14:
- The app references non-public selectors in Payload/xxxx.app/Frameworks/AWSAuthCore.framework/AWSAuthCore: reloadSession
- The app references non-public selectors in Payload/xxx.app/xxxx: applicationWillEnterForeground
don't worry these are warning only. but AWSCore have not released anything official yet. i got this warning after updating to xcode 14.
my app is published to test-flight and my testers are able to download and test.
don't worry these are warning only. but AWSCore have not released anything official yet. i got this warning after updating to xcode 14.
my app is published to test-flight and my testers are able to download and test.
warnings are something to be worry, even if it's for a misspelling typo and should be fixed. So we worried and should be fixed or that's how you start coming with problems later...
This is an issue with Apple's code validation. As of 10/31/2022, this is still an issue with Xcode 14.1 RC2.
This validation issue is not specific to AWS iOS SDK. See references to the same issue in other code bases:
- https://issuetracker.google.com/issues/246667837
- https://developer.apple.com/forums/thread/714736
- https://developer.apple.com/forums/thread/713574
- https://github.com/facebook/react-native/issues/34716
Note: This issue does not block or prevent TestFlight submissions or App Store Connect approvals.
We are deferring and waiting for Apple to fix this issue in their code validation. Fixing this issue in AWS iOS SDK as a workaround would require a signature rename and introduce a breaking change. If this becomes a blocking issue in the future, we have the fix ready in PR #4366
I faced a similar warning message when trying to upload my app to TestFlight using Xcode 14.
Ok, I found a solution I used Transporter utility to upload binary, I didn't find any warning in logs.
Ok, I found a solution I used Transporter utility to upload binary, I didn't find any warning in logs.
That's a workaround, not a solution.
Currently, I cannot upload to TestFlight with this warning! Xcode 14.2. Any solutions??
@yanbai100624 I just uploaded a new test app to AppStoreConnect without any issues using Xcode 14.2.
Previously, I was observing app uploads would succeed but with a warning message, it did not block any upload. With 14.2 I can successfully upload with no warning.
Can you clarify why or what is blocking your app upload? What are the error logs or screenshot that you can provide? For my testing, I archived the app and then uploaded using Xcode 14.2; both validation and distribution step succeeded with no warnings.
