Repository navigation
Description
Description
Submitting a React Native app build to the Apple App Store results in a rejection email regarding "Non-public API usage".
Dear Developer,
We identified one or more issues with a recent delivery for your app, "AppName" 1.0.0 (1.2.0). Please correct the following issues, then upload again.
ITMS-90338: Non-public API usage - The app references non-public selectors in AppName: centerY, hide:, isPassthrough, onSuccess:, permissionType, removeValuesForKeys:completion:, setLabelText:, show:, valueOffset, viewManager. 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
Version
0.68.1
Output of npx react-native info
System:
OS: macOS 11.6.4
CPU: (8) arm64 Apple M1
Memory: 148.92 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.0.0 - ~/.nvm/versions/node/v16.0.0/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v16.0.0/bin/yarn
npm: 7.10.0 - ~/.nvm/versions/node/v16.0.0/bin/npm
Watchman: 2022.02.28.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.68.1 => 0.68.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
1:Archive App(Release scheme)
2:Upload the resulting .ipa file to App Store Connect via Transporter (available on the Apple App Store)
3:Receive an email from apple that the build was rejected.

Activity
cortinico commentedon May 9, 2022
Which engine are you using?
Tak-As commentedon May 9, 2022
How can I find out?
Tak-As commentedon May 9, 2022
I'm using 'jsc' engine. not hermes.
Tak-As commentedon May 10, 2022
I upgraded the OS to Monterey12.3.1, but there is no change.

However, in Xcode 13.3.1, the Validate App fails. (No error if Xcode 13.2.1)
Andressaray commentedon May 12, 2022
I have the same issue, won't let me upload version to Testflight and I dont know the reason.
fortmarek commentedon May 16, 2022
Hey, there is a PR trying to address a similar thing - can you confirm you are trying to upload an app in debug mode? Any additional information about the issue would be helpful here @Tak-As @Andressaray
brentvatne commentedon May 16, 2022
Hi there! Are you using
expo-dev-client? Also, can you make sure you are using the latest version of theexpopackage - the latest as of writing is 45.0.4.Tak-As commentedon May 17, 2022
Thanks for reply.
In my environment ("react-native": "0.68.2") the result is the same in debug mode and release mode.
I can expect that my problem will be solved if the PR is merged.
Thanks for reply.
Yes, I was install "expo-dev-client". but my project is rejected expo.(bare workflow)
Build fails when upgrading to expo 45.0.4 & expo-dev-client 0.9.5. (Command PhaseScriptExecution failed with a nonzero exit code)
34 remaining items
jwoo92 commentedon Jun 7, 2022
Thanks for the callout, @bennsandoval.
Tried uploading again and found success.
Tak-As commentedon Jun 29, 2022
I solved it once, but the problem occurred again.
Is it just my problem?
paulocoutinhox commentedon Jun 29, 2022
Update the macOS to Mojave and Xcode to latest version.
Tak-As commentedon Jul 19, 2022
This issue has not yet been resolved.
Many people seem to be able to fix it by changing the schema to a release, but it doesn't seem to work in my environment.
Is there any workaround for the issue where the release build doesn't work?
thank you.
airowe commentedon Aug 5, 2022
Seeing the same issue as @Tak-As. Building a release scheme. Debug mode works just fine.
abazudosen commentedon Sep 3, 2022
how did you solve it
diegogurpegui commentedon Sep 3, 2022
I didn't. It was an Apple issue, after a day it was sorted out and, without doing anything different, it worked.
mvniekerk commentedon Sep 17, 2022
Still an issue.
Even with blank new ejected Expo app.
I've logged a report here #34716
saad9624-tribalScale commentedon Oct 11, 2022
Still getting the same issue with newer version of xcode i.e 14.2
prakarti-shush commentedon Oct 18, 2022
getting the same issue with newer version of Xcode 14
kelset commentedon Oct 18, 2022
This issue has gone in many different directions (in some cases it's Apple's backend, in some it's Expo-related, etc etc) and there's no clear repro that pinpoints how this is a specific issue caused by react-native core itself.
I am closing this so if anyone has this issue with the latest version of react-native 0.70 (NOT EXPO) they can open a new issue with a clear, usable repro so that it can be investigated further.