react-native-fcm: [IOS] The app crash at start
I’m using RN 0.43.2, iOS 5s (10.2) Simulator and Xcode 8.2.1.
I do well the installation steps but the app crash in iOS (I try using pod and in other copy of my project using without pod and nothing).
npm install react-native-fcm --savereact-native link react-native-fcm- edit Podfile and add
pod 'Firebase/Messaging' - edit AppDelegate.h
- edit AppDelegate.m
- I enable the necessary Capabilities
- In Manage schemes I remove and add the scheme of my project I do double click, click in Build and I add React and projectTest. And put in order React -> project -> projectTest.
I put the GoogleService-Info.plist file into project/ios/project/.
But I can’t do this run.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 7
- Comments: 16 (2 by maintainers)
This comment solved it for me. https://github.com/evollu/react-native-fcm/issues/322#issuecomment-281678346
I had the same issue. It looks like there are breaking changes in new version of Firebase pod (4.0.0). https://firebase.google.com/support/release-notes/ios#4.0.0
After downgrading it to previous version it works fine for me.
Just in case anyone finds their way to this issue (as I did) with a more recent setup, I encountered this issue with:
The issue arose due to me referencing legacy Firebase Cocoapods in my Podfile:
The fix was to match them to the version from https://github.com/evollu/react-native-fcm/blob/master/Examples/simple-fcm-client/ios/Podfile.lock (4.9.0)
Thanks @philjoseph it works now.
@tolgaduzenli we had the exact same issue (same stack trace) with this configuration (RN and RN-FCM versions) and with an upgrade of react-native-fcm to version 7.0.0, we’ve resolved that crash that keeps us busy (too) many days. I wonder if there is a way in npm to alert users that a version requires immediate attention, but I believe that most users with pre-7 version will hit this painful issue and would love to be notified.
I got this crash as well; this library doesn’t yet support the new FCM v4 on iOS, so I’ve opened an issue for it here: https://github.com/evollu/react-native-fcm/issues/422.
I got the same issue. The tricky thing is that in my case it has the problem on both ios simulator and real ios device, but only my simulator can still receive a message from firebase cloud message. Could anyone help? thank y’all.
Xcode version: 8.3.2 React-native: 0.44.0 React: 16.0.0-alpha.6 react-native-fcm: 6.2.3
Some error message: 1.)[warn][tid:NSOperationQueue 0x6000000371a0 :: NSOperation 0x608000247500 (QOS: DEFAULT)][RCTModuleData.mm:220] RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks
2.)[88247:886530] Unable to connect to FCM. Error Domain=com.google.fcm Code=2001 “FIRMessaging is already connected” UserInfo={NSLocalizedFailureReason=FIRMessaging is already connected} ==> It keeps saying this, but my ios simulator still can receive FCM msg.
3.)[RNFIRMessaging messaging:didRefreshRegistrationToken:]: unrecognized selector sent to instance 0x6080002356a0
4.)Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: '-[RNFIRMessaging messaging:didRefreshRegistrationToken:]: unrecognized selector sent to instance