服务器 api 键：迁移文档 vs 迁移视频
Server api key: migration doc vs migration video
GCM -> FCM migration doc需要的唯一改变是改变端点：
Update your server code to use new FCM endpoints for sending messages via HTTP and XMPP... Optionally, you may want to evaluate the FCM HTTP v1 API, which offers an improved security model and new capabilities for customizing messages across
但是 video 似乎讲述了一个不同的故事：
I'll need to update to a new more secure server key which I can get from the firebase console... download the service account credentials then I'll drag the JSON file into my project... replace the GCM API key with this service account key I'll update my HTTP header to use this access token...
我们可以在向新的 FCM 端点发送请求时继续使用 GCM 服务器 api 密钥，还是 "need to update to a more secure server key" 从 FCM 控制台获取？
您指出的 GCM 文档有点（不是那么多）旧。它显示了从 GCM 迁移到 FCM Legacy 时需要更改的内容。 Jen Person 在视频中展示的是你何时使用 FCM v1 (see the uri on 8:19).
Can we continue to use the GCM server api key when sending requests to the new FCM endpoint or do we "need to update to a more secure server key" obtained from the FCM console?
来自我的评论 here（有少量更新）：
Depending on which type of GCM API Key you were using (if this is a reeeaally old project, you might still be using a different type of Key), it may not work. Regardless, after you import your GCM project to Firebase, it would probably generate the necessary API Keys (Server Key for this matter) that you could (and should) use in order for FCM to work.
GCM -> FCM migration doc需要的唯一改变是改变端点：
Update your server code to use new FCM endpoints for sending messages via HTTP and XMPP... Optionally, you may want to evaluate the FCM HTTP v1 API, which offers an improved security model and new capabilities for customizing messages across
但是 video 似乎讲述了一个不同的故事：
I'll need to update to a new more secure server key which I can get from the firebase console... download the service account credentials then I'll drag the JSON file into my project... replace the GCM API key with this service account key I'll update my HTTP header to use this access token...
我们可以在向新的 FCM 端点发送请求时继续使用 GCM 服务器 api 密钥，还是 "need to update to a more secure server key" 从 FCM 控制台获取？
您指出的 GCM 文档有点（不是那么多）旧。它显示了从 GCM 迁移到 FCM Legacy 时需要更改的内容。 Jen Person 在视频中展示的是你何时使用 FCM v1 (see the uri on 8:19).
Can we continue to use the GCM server api key when sending requests to the new FCM endpoint or do we "need to update to a more secure server key" obtained from the FCM console?
来自我的评论 here（有少量更新）：
Depending on which type of GCM API Key you were using (if this is a reeeaally old project, you might still be using a different type of Key), it may not work. Regardless, after you import your GCM project to Firebase, it would probably generate the necessary API Keys (Server Key for this matter) that you could (and should) use in order for FCM to work.