英文:
Does anyone know what to do in case of legacy Firebase Cloud Messaging (FCM) APIs will be discontinued?
问题
我收到了来自Firebase的电子邮件，其中提到从2024年6月20日开始，将停止使用传统的Firebase Cloud Messaging (FCM) API。
我已经仔细阅读了文档并进行了谷歌搜索，但我没有找到替代解决方案。如果有人有额外的想法，请帮助我。
英文:
I got an email from Firebase saying that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.
I read the document thoroughly and googled my question, but I could not come up with an alternative solution. Please assist me if anyone has any additional ideas.
答案1
得分: 4
抱歉，你收到的消息可能不够清晰。它应该包含一个将被停用的 API 列表（它们已经在很多年前被弃用），以及要调用的新 API。如果这些信息没有正确显示，你也可以在 2023 年 6 月 Firebase 云消息传递功能常见问题解答 中找到这些信息。
我不会在这里重复列出所有的 API，因为它们相当多。要了解的重要事情是，版本化的 API 已经在多年前引入，并在 Firebase 文档中有记录，例如在 发送消息 上的文档，例如 构建发送请求。如果你的代码仍然使用旧的 API，也有一个关于 从旧版 FCM API 迁移到 HTTP v1 的页面。
英文:
firebaser here
Sorry if the message you received wasn't clear. It should contain a list of the API that will be discontinued (they were deprecated many years ago already) and the new API to call. If that somehow didn't show up correctly, you can also find the information in the FAQ on FCM features deprecated in June 2023.
I'm not going to repeat all the APIs here as its quite a list. The important thing to realize is that the versioned API was introduced years ago already, and is documented in the Firebase documentation on sending messages for example on building send requests. If you have code that still uses the legacy API, there's also a page on migrating from legacy FCM APIs to HTTP v1.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论