FR: Add Support for getting all topics

[codekeyz]

Consider adding support for getting all the topics in the various Admin SDK's so that we developers can adequately manage topics from our codebase.

[chong-shao]

Hi codekeyz. We are planning on adding this feature to the AdminSDK (along with a new HTTP API). But we don't have an estimated timeline now.

[codekeyz]

@chong-shao okay, that's fine

[sovlful]

is there any news about this fr?

[chong-shao]

@sovlful also mentioned in the other thread #1568
"it would be cool if this API could return topics and the number of users subscribed to each one, in order to know which topics are more popular than others"

[chong-shao]

Currently there's still no estimated time for supporting this feature. Let's continue gathering requests in this thread. This would help the FCM team to determine the details in offering this feature.

[TomBeckett]

This would be hugely useful for me. Especially when debugging users not receiving messages.

Right now, its a total black box when it comes to who is subscribed to what.

[MightySepp666]

@chong-shao This is a very important feature, that is still missing in the HTTP API v1. We are storing a user's subscribed topics in our backend. However, since the Firebase backend occasionally fails (due to rate limits or outages), a mechanism for synchronizing the subscribed topics is absolutely necessary.

Right now we still need to use the deprecated Instance ID API to accomplish this: https://iid.googleapis.com/iid/info/${deviceId}?details=true.

Can you tell me, if the Instance ID API will also be affected by the shutdown of the legacy FCM API in June?

It's really frustrating, that Firebase keeps removing useful APIs without having any replacement (like you did with the sendMulticast() method).

[MightySepp666]

@chong-shao could you please tell me, if the Instance ID API will also be affected by the shutdown of the legacy FCM API in June?

[boxymoron]

@chong-shao

Are there any non-deprecated alternatives to https://iid.googleapis.com/iid/info/${deviceId}?details=true in 2024?

Same as @MightySepp666, the current API needs/is missing a mechanism for synchronizing devices and topics in FCM, as that is the 'source of truth'. Although we store device ids and topic subscriptions in 'our DB', managing such subscriptions from FCM would be preferred, as it would ensure consistency.