Gmscore: "$app_name won't run properly until you update Google Play Services"

Created on 27 Aug 2018 · 7Comments · Source: microg/GmsCore

An increasing number of apps start to ask for an updated version of Google Play Services, after they received an update themselves.

The most recent ones where Discord and Protonmail. Discord seems to use ReCaptcha now that fails to show so the app is unusable. Protonmail seems to work so far but I need to do more testing before I can be sure.

How can I assist you in finding the issue with this? You probably need a logcat but of what app(s) or service(s) in particular?

I will then try to provide you with those logs.

Both apps are free btw so you could try to reproduce it.

https://play.google.com/store/apps/details?id=ch.protonmail.android

https://play.google.com/store/apps/details?id=com.discord

Source

DPTJKKVH

👍1

Most helpful comment

Fixed in v0.2.5.12879 / 4040e3df85db5dd59ed3028978a33eb92d7f4e46.

mar-v-in on 28 Aug 2018

👍5 ❤3

All 7 comments

Same:

08-27 11:36:53.697 14473 18102 W ContextImpl: Failed to ensure /data/user/0/com.google.android.gms/shared_prefs: mkdir failed: EACCES (Permission denied)

08-27 11:36:53.713 14473 18102 W GooglePlayServicesUtil: Google Play services out of date. Requires 12451000 but found 12221403

08-27 11:36:54.001 17601 17601 W GeckoApplication: STARTUP PERFORMANCE WARNING: un-official build: purging the startup (JavaScript) caches.

08-27 11:36:54.136 1042 1169 I ActivityManager: Displayed com.Slack/.ui.NotificationSettingsActivity: +539ms

This is with Slack's "troubleshoot notifications" feature on a MicroG build of LineageOS.

Tyler-2 on 27 Aug 2018

590 looks like a more app-specific dupe.

Tyler-2 on 27 Aug 2018

Turns out this is absolutely nothing new... In the past the GMS version would just get bumped, but now there are functional differences that must also be built in. PR #553 shows some of the discussion around this. And the sole maintainer of this software is over burdened to handle it on his or her own. :-(

Tyler-2 on 27 Aug 2018

Fixed in v0.2.5.12879 / 4040e3df85db5dd59ed3028978a33eb92d7f4e46.

mar-v-in on 28 Aug 2018

👍5 ❤3

See the update for MicroG Services Core to version 0.2.5.12879. Appears to have done the trick. Thanks Mar-V-In!

Tyler-2 on 28 Aug 2018

@mar-v-in Thanks Marvin. I'll send some money your way soon!

I assume those will be included with the next LineageOS for microG ROMs as well as released as an update to F-Droid, right?

DPTJKKVH on 28 Aug 2018

Thank you very much. Hopefully the next LineageOS for MicroG whyred build will pull these changes.