Skip to content

java.lang.IllegalArgumentException: No enum constant com.google.firebase.ErrorCode.UNIMPLEMENTED #974

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

Closed
cgdsyilmaz opened this issue Aug 12, 2024 · 8 comments

Comments

@cgdsyilmaz
Copy link

cgdsyilmaz commented Aug 12, 2024

Hello,

We are receiving IllegalArgumentException while calling com.google.firebase.messaging.FirebaseMessaging#sendMulticast(com.google.firebase.messaging.MulticastMessage) method since 2024-08-12 13:44 GMT. We are using 9.1.1 version of firebase-admin dependency.

Here is the exception detail:

java.lang.IllegalArgumentException: No enum constant com.google.firebase.ErrorCode.UNIMPLEMENTED
	at java.lang.Enum.valueOf(Unknown Source)
	at c.g.f.m.FirebaseMessagingClientImpl$MessagingBatchCallback.createFirebaseException(FirebaseMessagingClientImpl.java:271)
	at c.g.f.m.FirebaseMessagingClientImpl$MessagingBatchCallback.onFailure(FirebaseMessagingClientImpl.java:258)
	at c.g.f.m.FirebaseMessagingClientImpl$MessagingBatchCallback.onFailure(FirebaseMessagingClientImpl.java:243)
	at c.g.a.c.googleapis.batch.BatchUnparsedResponse.parseAndCallback(BatchUnparsedResponse.java:209)
	at c.g.a.c.googleapis.batch.BatchUnparsedResponse.parseNextResponse(BatchUnparsedResponse.java:149)
	at c.google.api.client.googleapis.batch.BatchRequest.execute(BatchRequest.java:269)
	at c.g.firebase.messaging.FirebaseMessagingClientImpl.sendBatchRequest(FirebaseMessagingClientImpl.java:138)
	at c.g.firebase.messaging.FirebaseMessagingClientImpl.sendAll(FirebaseMessagingClientImpl.java:118)
	at com.google.firebase.messaging.FirebaseMessaging$2.execute(FirebaseMessaging.java:295)
	at com.google.firebase.messaging.FirebaseMessaging$2.execute(FirebaseMessaging.java:292)
	at com.google.firebase.internal.CallableOperation.call(CallableOperation.java:36)
	at com.google.firebase.messaging.FirebaseMessaging.sendAll(FirebaseMessaging.java:183)
	at com.google.firebase.messaging.FirebaseMessaging.sendMulticast(FirebaseMessaging.java:254)
	at com.google.firebase.messaging.FirebaseMessaging.sendMulticast(FirebaseMessaging.java:227)....

Is there a chance that a deprecated resource was deleted today? In any case, we are switching to the sendEachForMulticast method as suggested.

@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@GideonCallbus
Copy link

GideonCallbus commented Aug 13, 2024

same thing happening here as well. does anybody want to share any workaround?

tested upto 9.3.0 and still have no idea why the MessagingServiceErrorResponse's holding seemingly unintended status 'UNIMPLEMENTED'.

@emindeniz99
Copy link

sendMulticast is unsupported since 22 july 2024 gradually they remove support from users.
you can check the issue #834 (comment)

@GideonCallbus
Copy link

sendMulticast is unsupported since 22 july 2024 gradually they remove support from users. you can check the issue #834 (comment)

Yes indeed! Thanks for clearly pointing that out 👍
..yet still com.google.firebase.ErrorCode.UNIMPLEMENTED shall be added I think.

@cshancj
Copy link

cshancj commented Aug 13, 2024

FYI @GideonCallbus

FCM will start a gradual shutdown of deprecated APIs around July 22nd, 2024. After this date, deprecated services will be subject to a "flickering" process in which increasing numbers of requests will return error responses. During the gradual ramp-down period you can expect the following behavior and error responses to increase in frequency over time:

@cgdsyilmaz
Copy link
Author

sendMulticast is unsupported since 22 july 2024 gradually they remove support from users.

you can check the issue #834 (comment)

Thank you for pointing this out. However a smoother transition from the deprecated resource to the new one could have been planned.

Changing to the new sendEachForMulticast api fixed this, if anyone is still looking for a solution.

@hezhijie
Copy link

mark

@lahirumaramba
Copy link
Member

I am closing this issue as switching to sendEachForMulticast() is the right approach here

@firebase firebase locked as resolved and limited conversation to collaborators Aug 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants