Can we access your project?
Current Behavior
Hello FlutterFlow Team,
I'm experiencing a dependency conflict with a newly exported FlutterFlow project when trying to add Firebase Cloud Messaging.
The exported project includes the following dependencies:
firebase_core: 3.14.0
firebase_core_platform_interface: 5.4.0
firebase_core_web: 2.23.0
When I try to add firebase_messaging, Pub fails with the following error:
Because my_trade_pal depends on both firebase_core_platform_interface 5.4.0 and firebase_messaging ^16.x.x, version solving failed.
Recent versions of firebase_messaging require firebase_core_platform_interface 6.x or 7.x, but the exported project pins it to version 5.4.0, making it impossible to install firebase_messaging.
I confirmed that the exported project directly depends on firebase_core_platform_interface 5.4.0, rather than it being pulled in transitively.
Could you please confirm whether this is an issue with the generated pubspec.yaml? If so, is there a recommended way to integrate firebase_messaging into a FlutterFlow-generated project without manually modifying the generated dependencies?
Thank you for your help.
Expected Behavior
I should be able to add the firebase_messaging package to a newly exported FlutterFlow project without dependency conflicts. The exported pubspec.yaml should contain compatible Firebase package versions so that FlutterFire packages (such as firebase_messaging) can be added successfully using flutter pub add or flutter pub get without requiring manual modification of generated dependencies.
Steps to Reproduce
You can use:
Create or open a FlutterFlow project.
Export the Flutter project.
Open the exported project in a terminal.
Run flutter pub get.
Attempt to add Firebase Messaging by running:
flutter pub add firebase_messaging:^16.4.1
Observe that dependency resolution fails with a version conflict involving firebase_core_platform_interface.
Reproducible from Blank
Bug Report Code (Required)
Not available
Visual documentation
Not available
Environment
- FlutterFlow version:
- Platform:
- Browser name and version:
- Operating system and version affected:
Additional Information
No response
Can we access your project?
Current Behavior
Hello FlutterFlow Team,
I'm experiencing a dependency conflict with a newly exported FlutterFlow project when trying to add Firebase Cloud Messaging.
The exported project includes the following dependencies:
firebase_core: 3.14.0
firebase_core_platform_interface: 5.4.0
firebase_core_web: 2.23.0
When I try to add firebase_messaging, Pub fails with the following error:
Because my_trade_pal depends on both firebase_core_platform_interface 5.4.0 and firebase_messaging ^16.x.x, version solving failed.
Recent versions of firebase_messaging require firebase_core_platform_interface 6.x or 7.x, but the exported project pins it to version 5.4.0, making it impossible to install firebase_messaging.
I confirmed that the exported project directly depends on firebase_core_platform_interface 5.4.0, rather than it being pulled in transitively.
Could you please confirm whether this is an issue with the generated pubspec.yaml? If so, is there a recommended way to integrate firebase_messaging into a FlutterFlow-generated project without manually modifying the generated dependencies?
Thank you for your help.
Expected Behavior
I should be able to add the firebase_messaging package to a newly exported FlutterFlow project without dependency conflicts. The exported pubspec.yaml should contain compatible Firebase package versions so that FlutterFire packages (such as firebase_messaging) can be added successfully using flutter pub add or flutter pub get without requiring manual modification of generated dependencies.
Steps to Reproduce
You can use:
Create or open a FlutterFlow project.
Export the Flutter project.
Open the exported project in a terminal.
Run flutter pub get.
Attempt to add Firebase Messaging by running:
flutter pub add firebase_messaging:^16.4.1
Observe that dependency resolution fails with a version conflict involving firebase_core_platform_interface.
Reproducible from Blank
Bug Report Code (Required)
Not available
Visual documentation
Not available
Environment
Additional Information
No response