Firebase InstanceID has been removed - iOS builds failing
See original GitHub issueDescribe the bug
We are using fastlane
to build iOS apps. Since 11th of May 2021 our builds are failing with error message:
`@capacitor-community/fcm/ios/Plugin/Plugin/Plugin.swift:7:8: [31mno such module ‘FirebaseInstanceID’
import FirebaseInstanceID`
The Firebase iOS SDK (v8.0.0) is now available and Firebase InstanceID has been removed.
There is a migration guide on how to move from Instance ID to Firebase Installations.
Expected behavior After migration there should be no issues with this plugin.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:22
- Comments:13 (4 by maintainers)
Top Results From Across the Web
error: no such module 'FirebaseInstanceID' on ios
FirebaseInstanceID is deprecated now, that is why this error is coming. Remove import FirebaseInstanceID from your AppDelegate.swift and ...
Read more >Firebase Apple SDK Release Notes - Google
Breaking change: The deprecated Firebase InstanceID has been removed. Use Firebase Installations to manage app instance and use Firebase Messaging to manage ...
Read more >firebaseinstanceid not found android - You.com
Potentially this is due to an issue with the mock google-services.json, generated from the quickstart script. It seems to be missing the api_key...
Read more >Solve Capacitor error: no such module FirebaseInstanceID
If you have implemented Firebase Cloud Messaging for notifications, you had to add FirebaseInstanceID package in order to receive a FCM token.
Read more >Firestore pod failing after update - Hacking with Swift
I update my pods often, so the version my have been upgraded to 6.20 or ... Now it works, looks like they removed...
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 FreeTop 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
Top GitHub Comments
I also found a solution without having to change the plugin package.
You can go to
ios/App/Podfile
and add the desired FirebaseCore version like this underneath the existing pods:After you did the change, don’t forget to run
pod update
.For those having issues with cap v2, try adding this in your app podfile