- 最新
- 投票最多
- 评论最多
Hey there,
I've been down that road before, and that error message can be a bit frustrating, but fear not, we'll get you sorted. The issue seems to be a hiccup between Firebase and SNS during the platform application creation. Double-check that you've copied the API key correctly – it's easy to miss a character or space.
Now, about limiting the API key to the Android app, you're on the right track, but sometimes, these changes take a bit to propagate. Waiting a few hours might not be enough. Try giving it a bit more time, and if it still persists, consider rechecking the Firebase configurations.
Also, make sure the package name in your Firebase project matches the one you're using in your SNS platform application. Mismatched package names can lead to this kind of headache.
I've had my fair share of battles with these integrations, and patience has often been the key. Hang in there, and let me know if these suggestions do the trick.
相关内容
- 已提问 2 个月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 8 个月前
- AWS 官方已更新 3 年前
How did you find "Cloud Messaging API (Legacy)"'s server key. It's invisible to me.
I have also found it and need to reactivate it