iOS Build failed: unknown receiver 'SplashScreen'; did you mean 'RNSplashScreen'
See original GitHub issueHi, I’m facing the following issue on version 3.1.0 with Xcode 9 while building iOS app
node_modules/react-native-splash-screen/ios/RNSplashScreen.m:52:6: unknown receiver 'SplashScreen'; did you mean 'RNSplashScreen'?
Looking at RNSplashScreen.m:52:6, I found this
RCT_EXPORT_METHOD(show) {
[SplashScreen show];
}
When replacing SplashScreen by RNSplashScreen the build succeeds. But I’m wondering if it’s the right way to go.
Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:28
- Comments:9 (1 by maintainers)
Top Results From Across the Web
multiple EAS build migration issues - #9 by wodin - Expo Forums
This is the error set I am seeing, I think I have migrated and updated everything. ... unknown receiver '_moduleRegistry'; did you mean...
Read more >nectr-rn/react-native-splash-screen - npm
A splash screen API for react-native which can programatically hide and show the splash screen. Works on iOS and Android.
Read more >Expo SDK 46 iOS build failed in fastlane step - Stack Overflow
as we had no problem in local build, we change the xcode version from 13 to 14 on bitrise and it worked!
Read more >React Native Splash Screen - Devinfo
Build Splash Screen for IOS and Android in your React Native project. ... You can also watch the video tutorial on my Youtube...
Read more >Add a splash screen to a React Native app - Medium
Also note that I'm not an iOS nor Android developer, so some steps may surely be improved. I'll be happy to read how...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve create a pull request #266 to fix it.
Any news on this ticket? Currently the plugin is broken unfortunately.