"Firebase token is not known"

[blaueente]

Steps to reproduce

1. Troubleshoot notifications
2. Click "Run tests"
3. Click "Fix..:"

Outcome

What did you expect?

Tests run through

What happened instead?

"Firebase token is not known"

Your phone model

Pixel 6 Pro

Operating system version

Android 14 AP2A.240905.003.F1

Application version and app store

Element X Version 0.6.3

Homeserver

matrix.org

Will you send logs?

Yes

Are you willing to provide a PR?

No

[bmarty]

From the rageshake logs that you sent (thanks!):

java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: FIS_AUTH_ERROR

What happen if you click to "Attempt to fix"?

[blaueente]

From the rageshake logs that you sent (thanks!):

java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: FIS_AUTH_ERROR

What happen if you click to "Attempt to fix"?

It showed "Ensure that firebase token is available" for about a second, and then switched back to the error.
I submitted a log where I pressed the "fix" button multiple times.

[wrenix]

I use microg as firebase client. There the firebase token was dropped. Now it is impossible to reregister a new token (like it is on unifiedpush by reselect it AS provider).

So please add a Option to reregister EXA with a new token.

[spaetz]

Given the recent 'rotate FCM token when broken' MR, this issue should be closed now.