FirebaseCore was removed and is still needed by the code the plugin injects
See original GitHub issueDescribe the bug
The removal of FirebaseCore
here:
https://github.com/capacitor-community/fcm/commit/38f186b09525ee681360b4437ed38c1cc57cb981#r51330784
is causing compilation issues as the code the plugin injects actually uses it.
To Reproduce Steps to reproduce the behavior:
- Install version fcm
v1.1.1
into existing project - Try to compile using XCode
- You still get compilation issues.
Expected behavior No compilation issues
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
[firebase_core] CSP Violation in Firebase Core · Issue #9817
The dart code that triggers the firebase_core plugin to inject its own ... however this still requires you load them in from somewhere...
Read more >Firebase Android SDK Release Notes - Google
Internal refactor to remove dead code and obsolete features. ... The plugin no longer injects a firebase-core dependency under any circumstances.
Read more >Flutter iOS: How to fix "Could not build module `firebase_core`"?
Remove ios/Pods folder. Remove Podfile and Podfile.lock. Remove pubspec.lock. Open terminal and run these commands one after another
Read more >Unity 2019.1 Cloud Build errors with Firebase only IOS
I have no idea how to fix these errors yet help :( 5080: [Unity] Error (Not a directory) ... [Unity] Removing Assets/Infinity Code/Online ......
Read more >Flutter — Firebase FireStore CRUD Operations Using Provider
Before diving into the real coding part, let's see what are the plugins and assets required in this project. Firebase console: Project setup....
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
Yeah, I will patch asap
yes you right good catch. we should get rid of that import too