You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is a bug or more a feature request but very recently a new FCMv1 channel was added for the notification hub and it seems the service explorer is not able to show registrations of this type. I have my own custom tool for some specific operations and when I do a tag search this record is returned (you can ignore PPOI column as this is something based on the tag info):
Executing the same tag expression in the explorer doesn't seem to return any results
edit: Here is also a link to the page about the deprecation of the legacy FCM and introduction of FCMv1: link
The text was updated successfully, but these errors were encountered:
Google will deprecate the Firebase Cloud Messaging (FCM) legacy API by July 2024. You can begin migrating from the legacy HTTP protocol to FCM v1 on March 1, 2024. You must complete the migration by June 2024.
Will you or anyone else object if we remove the support for FCM legacy in the next release? If someone needs it, they can use the current release.
I can update SBE to use the new version of the Notification hubs SDK, but I won't be able to test it. Will you be able to verify the release? Perhaps build from source code?
Hello,
Not sure if this is a bug or more a feature request but very recently a new FCMv1 channel was added for the notification hub and it seems the service explorer is not able to show registrations of this type. I have my own custom tool for some specific operations and when I do a tag search this record is returned (you can ignore PPOI column as this is something based on the tag info):
Executing the same tag expression in the explorer doesn't seem to return any results
edit: Here is also a link to the page about the deprecation of the legacy FCM and introduction of FCMv1: link
The text was updated successfully, but these errors were encountered: