-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request: generate or support web/firebase-messaging-sw.js #215
Comments
This is a major headache and one which is hard to find the cause or a solution until you stumble on firebase/flutterfire#11678 |
For flavors when you generate that file: |
I think this is the official reference to how to create the service worker: |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
No it is not fixed yet |
+1 |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
No it is not fixed yet |
Is there an existing feature request for this?
Command
flutterfire configure --include-messaging
Description
Running "flutterfire configure" works like a charm for normal Firebase operations, but is missing out on Cloud Messaging assistance. We now need to still manually and hardcoded introduce our own firebase-messaging-sw.js for web.
Steps to reproduce the behavior:
Run "flutterfire configure"
Notice web/firebase-messaging-sw.js is not created
Expected behavior
web/firebase-messaging-sw.js or any working equivalent should be created, optionally through flag or always
Reasoning
messaging is important component of many apps.
Hardcoding should be avoided where possible
Additional context and comments
No response
The text was updated successfully, but these errors were encountered: