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

Line App Notification not working #186

Closed
dequegorg opened this issue Jun 17, 2021 · 9 comments
Closed

Line App Notification not working #186

dequegorg opened this issue Jun 17, 2021 · 9 comments

Comments

@dequegorg
Copy link

I have LineageOS for microG (lineage_sargo-userdebug 11 RQ2A.210405.005 eng.root.20210411.235807 dev-keys) installed on Pixel3a, together with Line App.

I wax expecting microG would fix the failing notifications in LineageOS, but it didn't. It seems Line app isn't subscribed to microG cloud notification. And according to the support flowchart this issue brings me here.

Expected behaviour: new incoming messages should push notification in background, while app is closed.

Problem: app is not sending notifications until opened.

Attempts at fixing: disabled battery oprimization for app, enabled background data usage, allowed all essential tracking on Tracker Control.

I'd like to troubleshoot and possibly fix the notification issue (I work a lot with this app). Thanks.

@bananer
Copy link
Contributor

bananer commented Jun 17, 2021

In the microG settings app, is Cloud Messaging enabled? Do you see Line App registered there?

@dequegorg
Copy link
Author

In the microG settings app, is Cloud Messaging enabled? Do you see Line App registered there?

Cloud Messaging enabled. Line App not registered there.

@bananer
Copy link
Contributor

bananer commented Jun 17, 2021

If cloud messaging works for other apps, this does not seem like an issue with microG or l4m. Is it a fresh install of Line App or did you restore from a backup? Could you try re-installing?

@dequegorg
Copy link
Author

Hi, I literally just installed LineageOS w/ MicroG yesterday and installed Line App on top. It's all fresh install.

Note: no application at all is listed under the Cloud Messaging settings of MicroG.

@Iey4iej3
Copy link

Iey4iej3 commented Jun 18, 2021

First, you need to check that Google device registration is on, and Cloud Messaging sets Receive push notifications. With these enabled, you could try

https://play.google.com/store/apps/details?id=com.firstrowria.pushnotificationtester&hl=en&gl=US

which is an open-source FCM tester, to see where the problem situates.

@dequegorg
Copy link
Author

dequegorg commented Jun 19, 2021

check that Google device registration is on

Check!

Cloud Messaging sets Receive push notifications.

Check!

Push Notification Tester

Prerequisites not met:

  • play services installed: check!
  • internet connectivity: check!
  • register for push notification: problem!
  • Connection to Server: check!

@Iey4iej3
Copy link

Iey4iej3 commented Jun 21, 2021

There are problems in the registration. Maybe you could read the logcat (for Push Notification Tester, which is with less irrelevant data than any app like Line), and upload it if you like (be careful: you have to suppress the confidential data in the logcat - note that once uploaded on GitHub, you have no way to delete it...)

@dequegorg
Copy link
Author

Hi, thanks. I collected the log. Thanks for the heads-up on data security. I trimmed what I thought seemed irrelevant. I hope I didn't remove anything useful:

https://pastebin.com/uZEMwqwE

@bananer
Copy link
Contributor

bananer commented Jun 21, 2021

I searched for "GmsGcmRegister: java.lang.RuntimeException: Checkin disabled" which led me to microg/GmsCore#1329

There are a few possible workarounds mentioned in that issue.

Seems like this is an issue with microG and not caused by lineageos4microg, so I will close this.

@bananer bananer closed this as completed Jun 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants