Skip to content
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

Server key #14

Open
cvrle77 opened this issue May 22, 2024 · 2 comments
Open

Server key #14

cvrle77 opened this issue May 22, 2024 · 2 comments

Comments

@cvrle77
Copy link

cvrle77 commented May 22, 2024

I cannot send notifications, unless I have 'server key' field populated, however, that field is from Cloud messaging Legacy API, while I am using http v1 API (or at least I want to use it)

image

That was a short version.
Longer version: I've seen issues by having same details in test and production website. So, I've opened new firebase project following your instructions. At the moment, Google is having issues with creating server key, while the rest of the details can be created. So I did that, and not entering server key details, because I don't have them.

Also, on Cloud Messaging tab, in Firebase, it says that I have to migrate from it by 6/20/2024, which means this key will be deprecated.
If we want to use only httpv1, do we only need to upload service account json file? Why do we need server key that will be deprecated?
image

There is no error message at any stage to suggest that I am doing something wrong. There is no notification history, so I can see that sending failed, or creation of it failed, or message that I am missing server key.

@muraliwebworld
Copy link
Owner

In upcoming release i will make server key as optional, At present, old logic which checks for server key is empty or false (for legacy notification) is present and httpv1 notification logic is also added after that condition, due to this problem occurred, I will remove this condition in upcoming release. Until i release next version, if you want to use httpv1 version, just fill some characters in server key field, it will not use this field for httpv1 notification. httpv1 notification will work even if server key is invalid. I will update the logic in correct way to ignore this condition in upcoming release. It will take few more days on or before Monday i will release next version soon. Since i am working on PWA enhancement and also i am thinking to incorporate PWA app to native mobile app conversion to generate apk file directly in this plugin, that research is taking more time for me now. Until i release next release, please fill some characters in server key and use httpv1 notification.

@cvrle77
Copy link
Author

cvrle77 commented May 23, 2024

Oh, I didn't even try, because I didn't know it's possible :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants