-
-
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
Corona Warn App "Fehler bei der Kommunikation mit der Google Schnittstelle" #1171
Comments
Delete the app data of |
Fake Store had already been installed when this error occurred (I think it comes with LineageOS for microG). I deleted app data and did the re-setup, as you have suggested. There was no error message this time. But I should add to my previous post, that this error had not arrised immediately after installation and first start of the app, but only after I had force-stopped it and started it again later. |
I see, in case it happens again a logcat from the error message would be helpful, to see the full error log. |
I had the message appear aswell today, but got rid of it by tapping on the "Risikostatus" tile to load detail view and then it correctly synced with RKI and the message was gone and everything fine. Will collect a logcat with the message pops up again. |
The error message has appeared several times in the last days, unfortunately. However, checking the exposure notification keys seems to have worked after several retries. My logcat with the error notification:
There seem to be related messages in the logcat. This seems to be a successful check of exposure notification keys:
On the other hand, an error happened here:
|
I have a similar problem with Corona Warn App. At first, it seemed to work well. But after a few days, the app refused to connect to the servers to download exposure tokens from people that have been tested positive. It produced the error messages in the attached screen shots. I tried to delete the app data and even deleted and reinstalled the app, but none of that helped. The app refused to work right from the beginning after reinstallation. I even deleted all my captured tokens in MicroG, but that didn't help, either. Have you already identified the problem causing this behaviour? I would be extremely happy, if a solution would be found. Thanks for your effort! |
I have the same problem as @hubbty.
Exposure notifications were active for 15 days when this happend. Deleting data or reinstalling Corona-Warn app did not help. |
I also face the same problem (API error 8). After deleting the CWA app data, it's back to "unknown risk", but according to
Logcat of API error 8, which occurred after starting and quitting app several times (doesn't always occur):
Maybe something to do with the unknown fields? For me, the errors also occurred after 14 days of use.
|
In the corresponding issue in the official German android app repo, @kbobrowski asks asks whether "ApiException: 8" has the same meaning in the MicroG EN implementation as in the Google implementation. Does anybody have a clue? @mar-v-in? |
IIRC, this error code is emitted by the client library, thus it doesn't matter which service is used. 8 means |
I don't know if this does really matter, but I report here just in case. Please see the screenshots of the details given by Corona Warn App.
My system:
lineage-16.0-20200816-microG-cheeseburger
microG Services Core 0.2.12.203315 from F-Droid
de.rki.coronawarnapp_v37 from Aurora store (in app information "Version: 1.3.0")
Please let me know if you need further information.
The text was updated successfully, but these errors were encountered: