-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
0.2.4-111. Broken registration of push messages applications. #517
Comments
This is quite expected, see #510. |
I think it has nothing to do with version 0.2.4-111 since there are only minor changes, and none related to push messages. |
@ale5000-git That’s what I implicitly said. It applies to all currently existing version of μG. |
Strange thing, but yesterday I made an experiment. |
Is was coincidence ? |
On what hour did you run which attempt? Problems with SafetyNet/Certification started y-day precisely. |
Check #439 |
Possible workaround: |
The problem should be fixed in recent versions of microG GmsCore, I'm closing this for now. |
Hi and sorry for owful English.
It does not matter - clean install on pure noGapps firmware or update previous build (108). New applications are not registered in microG Google Cloud Messaging. It can be Viber, Telegram, VK etc.
The text was updated successfully, but these errors were encountered: