* Update privacy_de.html

* Update privacy_de.html

Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>

Release 1.7 to 1.8

Cannot delete tests older than 21 days - DE: Tests die älter als 21 Tage sind, können nicht gelöscht werden (EXPOSUREAPP-2398) (#1586)

* 1. Replaced redundant uiStateState during test result fetch with a NetworkRequestWrapper that is able to represent multiple states. This allows for better request state handling throughout the app
2. Completely removed the SubmissionViewModel
3. Failure to fetch the test should now always display the invalid test card on the home screen

Signed-off-by: Kolya Opahle <k.opahle@sap.com>

* Keep displaying fetching card on server errors as this usually does not indicate any problems with the test itself

Signed-off-by: Kolya Opahle <k.opahle@sap.com>

* Fixing unit tests (mostly just syntax, one test case changed due to new card)

Signed-off-by: Kolya Opahle <k.opahle@sap.com>

* Promoted unknown host exception to server exception

Co-authored-by: chris-cwa <69595386+chris-cwa@users.noreply.github.com>
Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

Merge 1.6.x into 1.7.x

Co-authored-by: Kolya Opahle <k.opahle@sap.com>
Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

* Enable logfile for tester builds by default.

* Fix test regression.

# Conflicts:
#	Corona-Warn-App/src/main/java/de/rki/coronawarnapp/nearby/modules/detectiontracker/ExposureDetectionTrackerStorage.kt
#	Corona-Warn-App/src/main/java/de/rki/coronawarnapp/util/flow/HotDataFlow.kt
#	Corona-Warn-App/src/test/java/de/rki/coronawarnapp/util/flow/HotDataFlowTest.kt
#	gradle.properties

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>

* Make config sharing behavior `SharingStarted.Lazily`. (start once, never release)
Otherwise classes that are just interested in the current config, if there is no other subscriber active,
would launch the `startValueProvider` and pull a config each time.

The ExposureDetectionTracker is such a candidate that would like to use the latest config every ~3min.

While this already no longer happens since "Track config changes" (4d1ecb54),
because there is no a class that is permanently subscribed to `currentConfig`, we should not rely on side-effects,
so let's make the sharing behavior explicit.

* Fix test regression.

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

* Fix HotDataFlow behavior.
* Prevent re-execution of past submissions when the observable goes cold.
* Guard internal value updates with a mutex in case the value update is not as thread-safe as we think it is.

* Fix problematic testcases.

* Update RiskLevelRepository.kt

* Removed comment

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

* Flush the json data after writing it, otherwise if the app process dies, we end up with an empty file.
GSON deserializes this into a null object that looks like a non-null object until it is evaluated some time later.

Force an evaluation via `require(it.size >= 0)` and delete the corrupt data file when catching the exception.

* Show a visible error dialog if we fail to save data.

* Used buffered versions of readers and writer.

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

* Catch cancellation exceptions for coroutines launched on the viewModelScope.

* Use the viewmodel provided launch method to use common handling.

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>
Co-authored-by: chris-cwa <69595386+chris-cwa@users.noreply.github.com>

Change-Id: I64e8b3a17346d3e14e3c7306c89100633afc104e

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>

* + config changed detector

* tests

* ConfigChangeDetector.kt improvements.
* Fix config collecting scoping
* Move the identifier update into the RiskLevelTask
* Add test coverage

* Logs NO-OPs too.

* Filter emissions early if the value didn't change.

* extracted constant

Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>

There is a number of place in the app with the following code pattern:

try {
    // do some suspending operation
} catch(e: Exception) {
    e.report(ExceptionCategory.EXPOSURENOTIFICATION) // or similar
}

In all such place if the corresponding suspending gets cancelled for any reason, the resulting CancellationException will get reported as an application crash. This fix prevents it from happening, since a cancellation exception is a part of a normal operation, not a failure that should be reported.

* Don't rename the APK on `device` flavor builds.
It breaks internal pipelines.

* Better log output.

* Update from https://github.com/corona-warn-app/cwa-protocol-buffers/commit/fb60eddacb048b9c0cd8a3c67ab728a9878611ed



* Include new default app config for v2.

Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>

Merge 1.7.x into 1.8.x (DEV)

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

* add TracingStatus check that forces No_Calculation option if exposure logging stopped

* detekt adjustments

* Added test with Rituraj for tracing status when tracing status is inactive

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

* If we revoked any cached keys we need to force an index lookup.
+ Additional tests to check that forced index lookup is decided on correctly.

* Fix merge regressions in tests.