400 BadRequestException on opening the app

Avoid duplicates

• Bug is not mentioned in the FAQ
• Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
• Bug is not already reported in another issue

Technical details

• Device name: Sony xz2c (xz2 compact)
• Android version: LineageOS 17.1 (Android 10) with MicroG (it worked flawlessly for many months in this setup)
• App version: CCTG 2.14.1.3

Describe the bug

On opening of the app, an error dialog is shown stating there was a bad request exception (HTTP status code 400). Dismissing it and continued use of the app is possible, but on closing the app and reopening, the dialog will reappear.

Steps to reproduce the issue

The app worked without this issue up to today, for over a year on the same phone with the same OS. I updated the CWapp recently but i’ve also used it afterwards, and this error only appeared this morning.

1. Open the CoronaWarnApp
2. Notice the error dialog

The full error test is:

de.rki.coronawarnapp.exception.http.BadRequestException: Error during web request: code=400 message= body='

de.rki.coronawarnapp.exception.http.BadRequestException: Error during web request: code=400 message= body='
 at de.rki.coronawarnapp.http.HttpErrorParser.intercept(HttpErrorParser.kt:80)
 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
 at de.rki.coronawarnapp.http.interceptor.RetryInterceptor.intercept(RetryInterceptor.kt:15)
 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
 at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.kt:154)
 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
 at de.rki.coronawarnapp.http.interceptor.WebSecurityVerificationInterceptor.intercept(WebSecurityVerificationInterceptor.kt:11)
 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
 at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
 at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
 at java.lang.Thread.run(Thread.java:919)

Screenshots:

<div> </div>

Expected behaviour

The app opens without showing any errors

Possible Fix

Dismissing the dialog will hide it, but it will come back after reopening the app.

Additional context

I have registered certifications in the app and rapid test profile. I keep the exposure notifications always on.

[dsarkar]

@vaubaehn So, I will leave it to the author @maricn of this issue to smile (since his issue was fixed e.g. or many other reasons) and close this issue. I definitely had to smile!

[vaubaehn]

@dsarkar You’re welcome. What does the label “read-to-close” mean - will the issue close itself after everyone read it? 😉 If it’s intended to function like this, then I’d favor “smile-to-close”.