You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We identified one or more issues with a recent delivery for your app, "App" 1.0 (7). Please correct the following issues, then upload again.
ITMS-90338: Non-public API usage - The app references non-public selectors in app: _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, isPassthrough, onSuccess:, removeValuesForKeys:completion:, setCategoryID:. 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
Reacted by Daniel Shneyder, Nikhila Mohan, David Wen Riccardi-Zhu, Edi Hasaj, Daniel Grossfeld, Steffen Thomsen, Douglas Nassif Roma Junior, mateoLorenzo1, Alex Hughes, Sean Flanagan and 18 more
Reacted by A.developer
Reacted by Zeeshan Ali Khan, Oleg Spatacovschi and A.developer
Reacted by Jose Ignacio, Fabrizio Botalla, Daniel Shneyder, Steffen Thomsen, Joshua Zhou, milobob, Dale Myszewski, Salvatore, Jane Manchun Wong, Dayan Ruben and 5 more
@ luan-nvg Isso parece semelhante ao problema 31437 . Você conseguiu fazer algum progresso nisso?
@luan-nvg This seems similar to Issue 31437. Were you able to make any progress on this?
I still couldn't get friend, this error is giving in the newest version of the react to 64, and the craziest is that if I put it in version 0.63 it doesn't give this problem, however according to them on the ipad version 14.5.1 of the problem. this week I had to hire a person to emulate my project on an ipad compatible with what they asked for, and the same works as they are rejecting the informant that there is a blank screen. without totally ridiculous log shipping.
Reacted by Salman Zindani, jackwullems, mateoLorenzo1 and Hazem Elshater
I found out that at 0.63 I was accusing blank screen only in the approval of the Apple ad, in my Xcode it was marked in the option Archive as debugging in Product / Scheme / Edit Sheme / Archive / Build Configuration, change to a non-debuggable release so I was able to pass in Apple.
Since the topic I opened went to 0.64 with the error Non-public use of the API, the topic will remain open.
EDIT:
Resolved this issue by updating my archive scheme from Debug to Release
Currently experiencing the same issue. I was previously able to build and publish 0.64 but today I got the same error when attempting to publish beta to testflight.
Reacted by Edi Hasaj, gasolin, Nabs, bernatbombi, Jack Dewhurst, scorpbittechnologies2022, zarvedan, Michel A., Ahmet Buğra Kara, Kanad Godse and 5 more
Reacted by linkplayer589 and AndreiO
Reacted by scorpbittechnologies2022, Ahmad Raza and linkplayer589
@luan-nvg
I was able to resolve my issue by updating my archive scheme from Debug to Release
Reacted by Jakub Boguski, scorpbittechnologies2022, Jeff Hughes, Max Harpunsky, Josue Mente, luan-nvg, Aditya Pujari, A.developer, jquartz, Andrew Duncan and 3 more
Reacted by Tak-As, milobob, Ali Monam, Imam Azis, Kapil Avaiya, H.P.Leung, gibo77, Ganpat Lakhara and toryry
Reacted by scorpbittechnologies2022, Ahmad Raza, Zaid Haroon, A.developer and Naeem ur Rehman
@luan-nvg
I was able to resolve my issue by updating my archive scheme from Debug to Release
our this same resolution I applied before seeing this comment at 0.63 was having a problem with white screen without much information from apple. and rra just because it was debug in the scheme. as soon as possible I will test on 0.64
Any solution on this?
Because I want to publish a test ipa on TestFlight with debug env. If I put scheme from Debug to Release, react-native-config will auto take Release value.
we're in same boat here, we need to publish our debug build to TestFlight for internal testing before release. this is blocking us from uploading to TestFlight. this was never an issue before.
Reacted by Daniel Grossfeld, Tamlyn Rhodes and Samuel Scheit
Hey all, any chance this issue is resolved without putting the whole project into release mode? Looks like I find myself in the same group using TestFlight...
Upgraded to react-native 0.66.0 and got this issue.
We need to publish our debug build to TestFlight for internal testing before release. this is blocking us from uploading to TestFlight.
Hey @arinjay, I found you can still upload to testflight in release mode as described by others above, but it will also get checked by apple as I understand. Since I am very inexperienced with the apple store, I am not sure what the impact of that will be and how setting the archive from "debug" to "release" really changes the version itself. Maybe somebody can shed a light?
uploading the app in release mode devoids us from opening the dev menu on apps downloaded from test flight.
Is there any method to override the dev menu to enable in release mode?
ITMS-90338: Non-public API usage - The app references non-public selectors in: _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/
Solved this by writing following post install script. uploaded app on Testflight in debug mode post making these changes and it got approved by Apple ✌️.
post_install do |installer|
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_modifierFlags",
"_modifierEventFlags")
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_modifiedInput",
"_modifiedEventInput")
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_isKeyDown",
"_isKeyEventDown")
find_and_replace("./node_modules/react-native/React/DevSupport/RCTPackagerClient.h",
"handleNotification",
"handlePackageNotification")
find_and_replace("./node_modules/react-native/React/DevSupport/RCTPackagerConnection.mm",
"handleNotification",
"handlePackageNotification")
end
definition of find_and_replace
def find_and_replace(dir, findstr, replacestr)
Dir[dir].each do |name|
text = File.read(name)
replace = text.gsub(findstr,replacestr)
if text != replace
puts "Fix: " + name
File.open(name, "w") { |file| file.puts replace }
STDOUT.flush
end
end
Dir[dir + '*/'].each(&method(:find_and_replace))
end
I used this code in my Podfile. When I run command pod install I get an error:
[!] Invalid Podfile file: [!] Specifying multiple post_install hooks is unsupported
I used this code in my Podfile. When I run command pod install I get an error: [!] Invalid Podfile file: [!] Specifying multiple post_install hooks is unsupported
@AndriyFedorovich As the error says, you already have a post_install block in your Podfile from the base RN install. Just move the find_and_replace lines from this tip into the one you had.
Solved this by writing following post install script. uploaded app on Testflight in debug mode post making these changes and it got approved by Apple ✌️.
post_install do |installer|
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_modifierFlags",
"_modifierEventFlags")
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_modifiedInput",
"_modifiedEventInput")
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_isKeyDown",
"_isKeyEventDown")
find_and_replace("./node_modules/react-native/React/DevSupport/RCTPackagerClient.h",
"handleNotification",
"handlePackageNotification")
find_and_replace("./node_modules/react-native/React/DevSupport/RCTPackagerConnection.mm",
"handleNotification",
"handlePackageNotification")
end
definition of find_and_replace
def find_and_replace(dir, findstr, replacestr)
Dir[dir].each do |name|
text = File.read(name)
replace = text.gsub(findstr,replacestr)
if text != replace
puts "Fix: " + name
File.open(name, "w") { |file| file.puts replace }
STDOUT.flush
end
end
Dir[dir + '*/'].each(&method(:find_and_replace))
end
For me it didn't work because of the relative paths starting with ./node_modules. (nothing was triggered)
However, I changed the paths to start with ../node_modules (notice the double dot indicating parent directory instead of current directory) and it worked (matched with "Fix: ..." output).
Solved this by writing following post install script. uploaded app on Testflight in debug mode post making these changes and it got approved by Apple ✌️.
post_install do |installer|
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_modifierFlags",
"_modifierEventFlags")
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_modifiedInput",
"_modifiedEventInput")
find_and_replace("./node_modules/react-native/React/Base/RCTKeyCommands.m",
"_isKeyDown",
"_isKeyEventDown")
find_and_replace("./node_modules/react-native/React/DevSupport/RCTPackagerClient.h",
"handleNotification",
"handlePackageNotification")
find_and_replace("./node_modules/react-native/React/DevSupport/RCTPackagerConnection.mm",
"handleNotification",
"handlePackageNotification")
end
definition of find_and_replace
def find_and_replace(dir, findstr, replacestr)
Dir[dir].each do |name|
text = File.read(name)
replace = text.gsub(findstr,replacestr)
if text != replace
puts "Fix: " + name
File.open(name, "w") { |file| file.puts replace }
STDOUT.flush
end
end
Dir[dir + '*/'].each(&method(:find_and_replace))
end
I used this code in my Podfile. When I run command pod install I get an error: [!] Invalid Podfile file: [!] Specifying multiple post_install hooks is unsupported
I use hybrid app setup (swift + react native), in case you node_module are present in different location. do check the path i ./node_modules/ (can try with ../node_modules/..)
Activity
skay97 commentedon May 17, 2021
@luan-nvg This seems similar to Issue 31437. Were you able to make any progress on this?
luan-nvg commentedon May 17, 2021
I still couldn't get friend, this error is giving in the newest version of the react to 64, and the craziest is that if I put it in version 0.63 it doesn't give this problem, however according to them on the ipad version 14.5.1 of the problem. this week I had to hire a person to emulate my project on an ipad compatible with what they asked for, and the same works as they are rejecting the informant that there is a blank screen. without totally ridiculous log shipping.
luan-nvg commentedon May 25, 2021
@skay97
I found out that at 0.63 I was accusing blank screen only in the approval of the Apple ad, in my Xcode it was marked in the option Archive as debugging in Product / Scheme / Edit Sheme / Archive / Build Configuration, change to a non-debuggable release so I was able to pass in Apple.
Since the topic I opened went to 0.64 with the error Non-public use of the API, the topic will remain open.
archcorsair commentedon Jun 12, 2021
EDIT:
Resolved this issue by updating my archive scheme from
DebugtoReleaseCurrently experiencing the same issue. I was previously able to build and publish 0.64 but today I got the same error when attempting to publish beta to testflight.
Method Names described in email (don't think all of these are RN, but some are):
archcorsair commentedon Jun 14, 2021
@luan-nvg
I was able to resolve my issue by updating my archive scheme from Debug to Release
luan-nvg commentedon Jun 15, 2021
our this same resolution I applied before seeing this comment at 0.63 was having a problem with white screen without much information from apple. and rra just because it was debug in the scheme. as soon as possible I will test on 0.64
archcorsair commentedon Jun 15, 2021
YourApp.xcscheme
WenLonG12345 commentedon Nov 15, 2021
Any solution on this?
Because I want to publish a test ipa on TestFlight with debug env. If I put scheme from Debug to Release, react-native-config will auto take
Releasevalue.haitaox commentedon Nov 15, 2021
we're in same boat here, we need to publish our debug build to TestFlight for internal testing before release. this is blocking us from uploading to TestFlight. this was never an issue before.
azeezat commentedon Dec 19, 2021
Navigate to ios/yourAppName.xcodeproj/xcshareddata/xcschemes/yourAppName.xcscheme and replace every instance of "Debug" with "Release"
SakeFabi commentedon Dec 25, 2021
Hey all, any chance this issue is resolved without putting the whole project into release mode? Looks like I find myself in the same group using TestFlight...
arinjay commentedon Jan 20, 2022
Upgraded to react-native 0.66.0 and got this issue.
We need to publish our debug build to TestFlight for internal testing before release. this is blocking us from uploading to TestFlight.
SakeFabi commentedon Jan 20, 2022
Hey @arinjay, I found you can still upload to testflight in release mode as described by others above, but it will also get checked by apple as I understand. Since I am very inexperienced with the apple store, I am not sure what the impact of that will be and how setting the archive from "debug" to "release" really changes the version itself. Maybe somebody can shed a light?
arinjay commentedon Feb 14, 2022
uploading the app in release mode devoids us from opening the dev menu on apps downloaded from test flight.
Is there any method to override the dev menu to enable in release mode?
100 remaining items
liho00 commentedon Mar 29, 2023
same issue GG
jacobleejones422 commentedon Apr 3, 2023
I am still getting this error

jaroslav009 commentedon Apr 10, 2023
ITMS-90338: Non-public API usage - The app references non-public selectors in: _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/
same issue
RenanSanguinete commentedon Apr 10, 2023
Same warning here.
The app references non-public selectors in Payload/ProjectApp.app/ProjectApp: getAuthorizationStatus:, isPassthrough, onSuccess:, removeValuesForKeys:completion
The Minimum Development already to 11.0
buildConfiguration set to "Release"
No Flipper enabled
React 0.68.5
Xcode 14.3
andrefilipin commentedon Apr 12, 2023
Same error here

jaroslav009 commentedon Apr 14, 2023
same gg
fabriciosautner commentedon Jun 6, 2023
Same problem
JanMesaric commentedon Jun 9, 2023
Same problem here.
"react-native": "0.71.10",
xcode 14.3.1
eas configuration updates
fedorovichandrey commentedon Jul 17, 2023
I used this code in my Podfile. When I run command
pod installI get an error:[!] Invalid
Podfilefile: [!] Specifying multiplepost_installhooks is unsupportedgreghaygood commentedon Jul 25, 2023
@AndriyFedorovich As the error says, you already have a
post_installblock in your Podfile from the base RN install. Just move thefind_and_replacelines from this tip into the one you had.guimarcel commentedon Mar 14, 2024
im using expo sdk 50, after 2 days searching answers to solve this bug and finally found the solution!!!
in eas.json
build.production.ios.buildConfiguration: true
and upload my build succesfully
Yasir12598 commentedon Apr 18, 2024
Thanks it works.
kavya-shree-s commentedon Nov 8, 2024
getting same error how did you resolved it
arinjay commentedon Jul 22, 2025
@kavya-shree-s try running this command
I use hybrid app setup (swift + react native), in case you node_module are present in different location. do check the path i ./node_modules/ (can try with ../node_modules/..)