Open maniaks1 opened 3 years ago
Is Firebase even maintained still? Just updated from my old 7.2 Firebase version to 10.7 to try some of the latest desktop support beta stuff, just to find that this crucial feature is broken since ages. That's ridiculous...
This is still happening on 11.6.0 I updated to the new version. I thought it sure is fixed as it was about 2 years ago and commented old dirty codes, but just not working 😇 I already spent another days to fix unity firebase-android plugin problem before this, and last week update just gone.
fb team all looking happy on youtube enjoying making their shit(= firebase for unity) long(=version ups for what?), like my AR book🤤
@paulinon @chkuang-g @cynthiajoan A statement would be nice. It's unbelievable that this is still not fixed!
Still not working...? I can't wait to work it.
Still problem on 11.9.0. anybody has some workaround for android and ios?
So here we are again, almost two years since I last commented, SDK 12.1.0 and this is still an issue.
To re-iterate, just calling GetTokenAsync() will not work, since it will only give you the token, the SDK is still broken and subscribing will NOT actually work.
Good news though, I did try the workaround suggested by [homu-konamilk] https://github.com/firebase/quickstart-unity/issues/1088#issuecomment-1308190083 and I can confirm that getting the token AND using the native java wrapper class does in fact work. This workaround seems much better than deleting the token and re-subscribing to all topics.
Makes you wonder how many Unity Android Apps have broken firebase integrations out there when everything seems fine first launch.
Anyway, hopefully someone finds this useful, try the aforementioned workaround. :)
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the question here:
After updating the Firebase Unity SDK from version 7.1.0 to version 8.0.0, the TokenReceived event on android stopped being called after each initialization. Now now the event comes only once when installing the application. On iOS, everything is still correct. A direct call to FirebaseMessaging.GetTokenAsync returns the push token correctly.
Is this a bug or a new behavior and now we need to get a token like in android sdk and save it until the next change?
=======================================================================================
Dependencies:
We are using manual initialization.
Android manifest:
Our initialization code:
=======================================================================================