Since 4 days ago my Volkswagen app stopped syncing. So I could not see the location and the battery percentage anymore. Today I tried deleting and reinstalling the app. Now it won’t even let me login. I think it has something to do Google services. Anyone a tip on how to fix this or is it even fixable?
Hi, first post here so i want say Hallo to everyone.
I instaled Volkswagen app from App Lounge and got similar issue. I can not login. Got message like that “Connection issue. Plesae try update your app or instsll it from your app store.”
Probably app checks something with integrity. Who knows how to debug it?
I use moto g82, with android 16, /e/os v3.7.3 Volkswagen 3.61.0
Same here. I checked/disabled all privacy settings, downloaded older apps. /e/os v3.7.3 and vw app from 3.61 → 3.58.2 (March). No change. So I assume Google changed security and microG / vw app needs an update.
Experiencing exactly the same thing, both on my Fairphone 3 running /e/OS 3.6t and my Fairphone 5 running 3.7.3 a15. It works fine on my wife’s Fairphone 4 running stock Android, so it should be /e/OS or MicroG related. Current version of the Volkswagen app (3.61.0) was released end of May, so that probably has something to do with it.
(I also tried reinstalling older versions of the Volkswagen app, but that did not make any difference.)
My VW app just stopped syncing. As I already told in another thread: clearing cache helped. But I never had to login again. That seams to be the main problem.
And I am using an official version of eos 3.7.3 (FP4).
Well yes, a log is one way to start to debug. There are any number of reasons why an app might fail … especially recently the chat in microG has included observations of new hurdles arriving weekly.
There is also the plexus link … where one can see reports of other people’s experience.
The Volkswagen WeConnect app initiates a security check using Google Play Integrity to verify the device’s safety. The system attempts to generate a security token and bind to the integrity service:
StandardIntegrity : warmUpIntegrityToken(992914193347)
StandardIntegrity : Initiate binding to the service.
2. Critical Error: Missing Google Account
The microG system component throws a critical warning. It cannot generate the required authentication token because no Google account is registered on the device:
[21:00:37.737] W/IntegrityExtensions: getAuthToken: No Google account found
[21:00:37.737] W/ExpressIntegrityService: warmUpIntegrityToken: Got null auth token for type: oauth2:https://www.googleapis.com/auth/googleplay
3. Login Window Closure and Return (Crash / Reset)
Because the integrity token returns a null value, the security verification fails. The embedded browser (WebView) intended for the login page is abruptly destroyed, causing the app to reset and throw you back to the home screen or previous app:
[21:00:37.726] W/cr_AwContents: WebView.destroy() called while WebView is still attached to window.
[21:00:37.714] D/VRI[IdentityKitWebHostActivity]: visibilityChanged oldVisibility=true newVisibility=false
In summary: Volkswagen has put up a wall in the form of Google security—a Google account must exist on the device for the app to work.
Access to their API is a different topic, but from my experience in IT, they’re probably trying to simplify things. Fewer client apps means fewer chances for data to leak.
Having same problem. I’ve tried signing into the app store with a system-wide Google account, and toggled Device Registration off/on in MicroG settings.
I’ll test in a more structured way when time allows.
Meanwhile, I have also been logged out and no further login is possible, as it happened to all of you. I contacted VW (connect-support@volkswagen.de) and they told me that this is because of third party programs that too often connected to their server and caused server problems (see the comment of @eos_fan). It seems that they prefer to loose clients instead of setting up some additional servers…
Anyhow, I told them that I am not using third party apps. It is the Volkswagen App which stops its function. They promised to forward this to the developers. But maybe that was just to get rid of me…
Nevertheless, maybe it is helpful if more than one person complains about malfunction of the app in case of /e/os. Feel free to send them further mails about this issue (see address above). Maybe that helps…