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.

Sign up for GitHub

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

Jump to bottom

errors don't parse #29

Open
dten opened this issue Jun 25, 2022 · 1 comment
Open

errors don't parse #29

dten opened this issue Jun 25, 2022 · 1 comment

Comments

@dten
Copy link

dten commented Jun 25, 2022 

"unknown variant `TOPICS_MESSAGE_RATE_EXCEEDED`, expected one of `MissingRegistration`, `InvalidRegistration`, `NotRegistered`, `InvalidPackageName`, `MismatchSenderId`, `InvalidParameters`, `MessageTooBig`, `InvalidDataKey`, `InvalidTtl`, `Unavailable`, `InternalServerError`, `DeviceMessageRateExceeded`, `TopicsMessageRateExceeded`, `InvalidApnsCredential`"

when fcm returns an error it seems that it returns in in SHOUTING_SNAKE_CASE but the parser expects Pascal
@dten
Copy link
Author

dten commented Jun 25, 2022

i realise i was using 0.7 of the code by accident, but i think this is still truee?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dten