Flutter Web Deployment Failing Due to web Package Dependency Conflict

[Skep-Angelo]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

My FlutterFlow project digi_market fails to deploy to Web after enabling Push Notifications with Web Push.

The Push Notification Cloud Functions deployment succeeds successfully. However, when I subsequently attempt to deploy the FlutterFlow web application, dependency resolution fails with the following error:

Because digi_market depends on cloud_functions_web 4.11.2 which depends on web ^1.1.1, web ^1.1.1 is required. So, because digi_market depends on web 1.1.0, version solving failed.

I checked Project Dependencies → Custom Pub Dependencies and FlutterFlow Pub Dependencies, but web is not listed in either section.

I also previously had a custom shareOnWeb action that used the web package. I removed this custom action completely and attempted the deployment again, but the exact same dependency conflict persists.

This suggests that the web 1.1.0 dependency is being introduced or pinned elsewhere in the generated Flutter project.

The issue prevents me from deploying the web/PWA version of my application after enabling Push Notifications.

Expected Behavior

The FlutterFlow project should successfully resolve its Dart dependencies and deploy to Web/PWA after enabling Push Notifications.

cloud_functions_web 4.11.2 requires web ^1.1.1, so I expect FlutterFlow to use a compatible version of the web package rather than generating or requiring web 1.1.0.

I also expect the dependency causing web 1.1.0 to be identifiable and configurable if it is coming from a project dependency or FlutterFlow-generated dependency.

Steps to Reproduce

1. Open the FlutterFlow project brasnding-site-455t3w.
2. Ensure the project is connected to the Firebase project aurenmarketplace.
3. Open Settings & Integrations → Push Notifications.
4. Enable Push Notifications.
5. Enable Web Push/PWA support and configure the Web Push Public VAPID Key.
6. Deploy the Push Notification Cloud Functions.
7. The Push Notification Cloud Functions deployment succeeds.
8. Attempt to deploy the FlutterFlow application to Web.
9. The Web deployment fails during Dart dependency version solving.
10. The deployment displays the following error:

Because digi_market depends on cloud_functions_web 4.11.2 which depends on web ^1.1.1, web ^1.1.1 is required. So, because digi_market depends on web 1.1.0, version solving failed.

11. Check Project Dependencies → Custom Pub Dependencies. web is not listed.
12. Check Project Dependencies → FlutterFlow Pub Dependencies. web is not listed.
13. Remove the previously existing custom shareOnWeb action that used package:web/web.dart.
14. Attempt the Web deployment again.
15. The same web 1.1.0 dependency conflict remains.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4wlsjfz4VOm99A1pDbbcAwoGAvIjp/R4Er0sIaQis8GZT0B4kcYs+kfklUOdO/S39APGGZmmMX/Mr8itjPG8A5OQ2Vc5xlyahMTwLLVmS6VaqODJS3b0EnDflMG0C13KuFoiVAXfBuR2Rg6mGmfvORcCzZHpDYOlYkDea4XdeK2SrDX1iXc2URm05KZDPz

Visual documentation

Environment

- FlutterFlow version: v7.0.78
- Platform: Web
- Browser name and version: Microsoft Edge Version 152.0.4191.66 (Official build) (64-bit)
- Operating system and version affected: Windows 11

Additional Information

This issue is currently blocking deployment of the DigiMarket web/PWA application.

I am enabling Push Notifications because DigiMarket needs merchants to receive notifications when customers place orders. The Push Notification Cloud Functions deploy successfully, but the application itself cannot be deployed to Web because of the dependency conflict.

The project does not expose web 1.1.0 in either Custom Pub Dependencies or FlutterFlow Pub Dependencies. Removing the custom shareOnWeb action also did not resolve the issue.

I therefore need help identifying where the web 1.1.0 dependency is being introduced and making it compatible with cloud_functions_web 4.11.2, which requires web ^1.1.1.