Cwa-app-android: App is not compatible with Samsung Galaxy A6 (year of purchase 2019)

[Peter-PA6]

Avoid duplicates

• [ x] Bug is not mentioned in the FAQ
• [ ] Bug is not already reported in another issue

Describe the xbug

Try to install from Google Play

Expected behaviour

App installs normally

Steps to reproduce the issue

Select Corona App from GooglePlay from Moble Phone Samsung Galaxy A6
Error Message appears:
Corona-Warn-App
Robert Koch-InstitutGesundheit & Fitness
PEGI 3PEGI 3
39.485
Diese App ist mit keinem deiner Geräte kompatibel.

Technical details

• iOS Version: Andriod 10
• Device: Samsung Galaxy A6

Possible Fix

Determine the cause of incompatibility
Update the App to resolve this

Additional context

[tens0rfl0w]

Is it possible that you are trying to install the app from a non-german Play Store account? Your screenshot shows the „PEGI“ instead of „USK“, so I will guess this from that information.

The „Corona-Warn“-App is currently only available in the German Play Store/App Store.

I would mark this as a possible duplicate of corona-warn-app/cwa-app-ios#623. Please see there for additional information about this „issue“ and possible workarounds.

MOD: Wrong repository, should be moved to the Android app repository.

[Peter-PA6]

How do I change the URL to a German site please?

I keep getting routed to this one in Google Play.
I have an 1&1 SIM card and I am connected via a Telekom -WLAN

[akuckartz]

@Peter-PA6 https://www.bundesregierung.de/breg-de/themen/corona-warn-app/corona-warn-app-kontakt-1759708

[realansgar]

@Peter-PA6 This isn't about a specific URL. Your Google account has to be set to Germany. This happens when you create your account or you can change it once a year in your account settings. This issue is being handled by SAP. Hopefully, the app will be released to the whole world in the near future. For further discussion, check out this issue: https://github.com/corona-warn-app/cwa-app-android/issues/478

[tkowark]

Having the app running on a Samsung A6 at home, this is indeed not a general issue but in your case seems to be the issue #478 instead. As written there and in many other issues, we're working on resolving that with the RKI and hopefully have some news on that soon.