Google Developer Console出现问题-GCM的发件人ID [英] Problems with Google Developer Console - Sender ID for GCM

查看:105
本文介绍了Google Developer Console出现问题-GCM的发件人ID的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我不是开发人员,而是需要发布使用twixl平台制作的数字信息亭杂志的图片.

I'm not a developer, but a graphic that needs to publish a digital kiosk magazine made with twixl platform.

我按照twixl文档的步骤为Android( FCM/GCM )上的通知创建了发件人ID.我创建了一个应用,在其中关联了发件人ID(API密钥),并且一切正常.我还拥有该应用程序处于活动状态的几天的统计信息.

I followed the steps of the twixl documentation to create a Sender ID for notifications on Android (FCM/GCM). I created an app where I associated a Sender ID (API key) and everything worked. I also have the statistics for a few days in which the app was active.

但是,对于证书问题,我不得不取消该出版物,并使用相同的帐户( app@pizzanew.it )再次出版.

For certificate problems, however, I had to cancel this publication and do another, from the same account (app@pizzanew.it).

在Google Cloud Platform中,我删除了旧项目,并创建了一个新项目.现在,当我进入Google Developer Console关联新ID时,它告诉我API密钥的值无效.

In Google Cloud Platform, I deleted the old project and I created a new one. Now, when I go to the Google Developer Console to associate a new id, it tells me that the value of API Key is not valid.

可能是它链接到了旧应用程序,还是某种我不知道的方式?但是旧的应用程序不再发布.

It may be that it is linked to the old app or in some way that I do not know? But the old app is no longer published.

我不知道该怎么做,但是我必须能够为通知设置此ID.我仅配置了新应用的常规信息,但尚未发布,并且我还没有上传新APK.可能是因为它吗?

I do not know how to do it, but I must be able to set this id for notifications. I configured only general information of the new app, but it has not yet been published, and I have not uploaded the new APK. May it's because of it?

感谢任何帮助.

推荐答案

有两个概念需要理解:

发件人ID :这是Google Cloud Console(对于旧项目)或Firebase Console(对于新项目)中的项目ID.

sender-id : this is the ID of the project in Google Cloud Console (for old projects) or Firebase Console (for new projects)

服务器密钥 :(也称为API密钥),这是服务器发送消息的密码".

server-key : (also referred as API-Key) this is the "password" for your server to send messages.

如果要更改您的SENDER-ID:

  1. 创建一个新的Firebase项目: https://firebase.google.com
  2. 阅读SenderId&服务器-键入设置
    (在哪里可以找到Firebase的API密钥云消息传递?)
  3. 更新您拥有的所有配置中的发件人ID
    (如果您使用的是FCM sdk,则需要下载新的google-services.json文件)
  1. create a new Firebase Project: https://firebase.google.com
  2. read the SenderId & Server-Key in the settings
    (Where can I find the API KEY for Firebase Cloud Messaging?)
  3. update the sender-id in all the configurations you have
    (if you are using the FCM sdk you need to download the new google-services.json file)

PS:如果您需要保留相同的发件人ID,则应该可以从Google Cloud Platform取消删除旧项目. 但是应在Firebase控制台中创建新项目,而需要新服务器密钥的旧项目应将旧项目导入Firebase控制台.

PS: you should be able to undelete the old project from Google Cloud Platform if you need to keep the same sender-id. But new projects should be created in Firebase Console, and old projects who need a new server-key should import the old project into the Firebase Console.

这篇关于Google Developer Console出现问题-GCM的发件人ID的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆