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

"Receive push notifications" and "Allow device attestation" toggles are greyed out #2002

Open
UnlimitedCookies opened this issue Aug 1, 2023 · 6 comments
Labels

Comments

@UnlimitedCookies
Copy link

UnlimitedCookies commented Aug 1, 2023

Both services seem to be broken and FCM shows disconnected state. I cannot toggle them off and microg doesn't give me a proper error message. Also, microg self-check shows that everything is fine.

No idea how to reproduce, but everything used to work perfectly.

Screenshots
Screenshot_20230801-234847_microG Services Core_1

System
Android Version: 12
Custom ROM: crDroid 8.7

Microg version 0.2.28.231657

@UnlimitedCookies
Copy link
Author

Here's what I found in the syslog searching for microg:

2023-08-02-00-01-23-microg-broken.txt

@UnlimitedCookies
Copy link
Author

Okay, after a restart the connection to FCM could be reestablished, but the toggles remain petrified.

@mar-v-in
Copy link
Member

mar-v-in commented Aug 1, 2023

From the log excerpt it looks as if device registration is disabled.

@UnlimitedCookies
Copy link
Author

From the log excerpt it looks as if device registration is disabled.

Correct, google device registration is disabled. Does that have to be enabled, because both FCM and Safetynet seemed to work with it being turned off.

@Sapiosenses
Copy link

From the log excerpt it looks as if device registration is disabled.

Correct, google device registration is disabled. Does that have to be enabled, because both FCM and Safetynet seemed to work with it being turned off.

Yes, it says right in the Cloud Messaging settings page that device registration must be enabled for that service to work.

If the device does not register to Google push servers, they do not know where to send the messages from your apps.

@UnlimitedCookies
Copy link
Author

Then the bug lies in me being able to sometimes use FCM without having my device registered.

  1. Why did this even work?
  2. Should the FCM settings page enforce the activation of device registration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants