Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: BatchResponse could return token of each message #364

Open
TupaNegreiros opened this issue Sep 22, 2023 · 1 comment
Open

FR: BatchResponse could return token of each message #364

TupaNegreiros opened this issue Sep 22, 2023 · 1 comment
Assignees
Labels
api: messaging type: feature request A new feature API is requested

Comments

@TupaNegreiros
Copy link

  • Operating System version: Win 10 22H2
  • Firebase SDK version: 2.4.0
  • Firebase Product: Messaging
  • .NET version: Framework 4.7

BatchResponse result = await messaging.SendMulticastAsync(message);

MulticastMessage has a List of tokens, SendMulticastAsync returns a BatchResponse with a list of message ids of succedded messages or exceptions of failed ones. BatchResponse could return the token string in each response, so we could associate each device token with success or failure.

@lahirumaramba lahirumaramba added the type: feature request A new feature API is requested label Sep 26, 2023
@lahirumaramba lahirumaramba changed the title BatchResponse could return token of each message FR: BatchResponse could return token of each message Sep 26, 2023
@474D
Copy link

474D commented Oct 1, 2023

@TupaNegreiros there was similar issue raised a while ago and authors previously answered that the order of batchResponse matches the tokens order in request, so you can actually map that manually :) (I hope that did not change, @hiranya911 can someone confirm this?). Ofcourse having explicit token in response would be way better 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: messaging type: feature request A new feature API is requested
Projects
None yet
Development

No branches or pull requests

5 participants