Incident: Users are unable to warn others

[Ein-Tim]

Avoid duplicates

• [X] Bug is not mentioned in the FAQ
• [X] Bug affects both Android and iOS, for specific issues / questions that apply only to one operating system, please raise them in the respective repositories:
  • Android repository
  • iOS repository
• [X] Bug is not already reported in another issue

Known affected devices

• OnePlus 8 Pro (Twitter)
• Pixel 4a (Codeberg)

Describe the bug

It seems like users are currently unable to warn others. See e.g.

• https://twitter.com/benebeuttler/status/1504080721933123584?s=21
• https://github.com/corona-warn-app/cwa-app-android/issues/4815#issuecomment-1069190376

Steps to reproduce the issue

Attempt to warn others.

Expected behaviour

Should be possible without issues.

---

Internal Tracking ID: EXPOSUREAPP-12297

[Ein-Tim]

Ping @mlenkeit & @thomasaugsten

[larswmh]

Thanks for your report @Ein-Tim. We have created an internal ticket for it and will raise this topic internally. Internal Tracking ID: EXPOSUREAPP-12297

---

Corona-Warn-App Open Source Team

[dsarkar]

@Ein-Tim Thanks for reporting. I just was informed that the issue has been fixed.

[Ein-Tim]

@dsarkar

Users are reporting that the problem persists: https://twitter.com/benebeuttler/status/1504122866224316417?s=21

[Ein-Tim]

More and more users are facing this problem: https://twitter.com/tom18954830/status/1504125138249424900?s=21, https://twitter.com/benebeuttler/status/1504122866224316417?s=21, https://twitter.com/timm_1991/status/1504124501419773957?s=21

@thomasaugsten Is there a fix insight? Else I will tweet about this.

[thomasaugsten]

There was a connection problem to the verification server. The problem should be solved since 3hours

do you have new reports in the last hour?

[Ein-Tim]

@thomasaugsten

Yes: https://twitter.com/tom18954830/status/1504158159925096462?s=21

[Ein-Tim]

Or what do you mean with "New", users who weren't affected before?

[Ein-Tim]

Here's another user: https://twitter.com/benebeuttler/status/1504159970287362050?s=21

Or do we have the situation here that all users who were affected will continue to see this error and can't warn others and now it is possible again for everyone else?

[citizenserious]

@Ein-Tim I tried it again, but there still is the same error .

Cause: de.rki.coronawarnapp.exception.TanPairingException: Tan has been retrieved before for this registration token at de.rki.coronawarnapp.playbook.DefaultPlaybook.wrapException(DefaultPlaybook.kt:131) at de.rki.coronawarnapp.playbook.DefaultPlaybook.submit(DefaultPlaybook.kt:114) at de.rki.coronawarnapp.playbook.DefaultPlaybook$submit$1.invokeSuspend(Unknown Source:15) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665) Caused by: 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:923)

[thomasaugsten]

With this error the user is not able to warn with the positive test. He needs to delete the test and warn via TAN.

[Ein-Tim]

@thomasaugsten Ok I will tweet this, thanks!

[Ein-Tim]

Closing, as the initial issue is fixed.

[haary]

He needs to delete the test and warn via TAN.

Does this mean, users with a rapid test who are getting the error (which have only a QR code and no TAN) aren't able to warn?