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

[Corona-Warn-App] v2.2.1 requires an update of Google Play-services (microG missing preConsent authorization?) #1469

Closed
Diapolo opened this issue May 13, 2021 · 3 comments

Comments

@Diapolo
Copy link

Diapolo commented May 13, 2021

Technical details

  • Device name: Fairphone 2
  • Android version: 10, LineageOS + microG version 0.2.19.211515
  • App version: 2.2.1

Describe the bug

I just tried to do the necessary steps for "Testergebnis abrufen" to learn any new workflows (I do this after each CWA update). When clicking on "Einverstanden" I now get an error message reading "Google Play-Dienste aktualisieren: Corona-Warn wird nur ausgeführt, wenn du die Google Play-Dienste aktualisierst". This was not the case with app version 2.1.2.

A CWA dev raised the idea, that my "microG version is not supporting the preConsent authorization introduced by Google 2 month ago". See: corona-warn-app/cwa-app-android#3163 (comment)

Steps to reproduce the issue

CWA1
CWA2
CWA3

Expected behaviour

Open the QR-Code reader.

Possible Fix

When tapping the error message the QR-Code reader opens. Not sure if registering a test would work, as I have none available to scan.

Additional context

I'm using LineageOS for microG, microG version 0.2.19.211515 (https://github.com/microg/GmsCore/releases/tag/v0.2.19.211515)

For reference, this is the issue in the CWA repo:
corona-warn-app/cwa-app-android#3163

@Diapolo Diapolo changed the title [Corona-Warn-App] version 2.2.1 requires an update of Google Play-services [Corona-Warn-App] v2.2.1 requires an update of Google Play-services (microG missing preConsent authorization?) May 13, 2021
@mar-v-in
Copy link
Member

Thanks for reporting. Indeed we can do something about this on microG-side (although CWA could have also had proper handling of this error on their side).

You might want to consider migrating to CCTG which is much better tested with microG and thus doesn't have this issue. See https://codeberg.org/corona-contact-tracing-germany/cwa-android#how-to-migrate-from-cwa on how to migrate.

@mar-v-in mar-v-in added this to the 0.2.20 milestone May 13, 2021
@Diapolo
Copy link
Author

Diapolo commented May 13, 2021

Thanks for fixing this :), is there any nightly or test-build available for verifying yet?

@mar-v-in
Copy link
Member

grote pushed a commit to grote/GmsCore that referenced this issue May 31, 2021
grote pushed a commit to grote/GmsCore that referenced this issue Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants