- Dec 09, 2020
-
-
Matthias Urhahn authored
Align coloring and padding with mockups.
-
- Dec 07, 2020
-
-
Katharina Seiz authored
Co-authored-by:
Matthias Urhahn <matthias.urhahn@sap.com>
-
chris-cwa authored
* fixed: fields without values are visible; + logs * detect version update, force recalc on 1.7 -> 1.8 * detect version update in diagnosis keys task only * no connection type ignoring * Add test to ensure that parsing old configs from 1.7.x fails and the default fallback for 1.8.x is used. * Fix logging typo. * no wasLastDetectionPerformedRecently abort on app update * Fix lint issues * fixed condition * used shared settings * get last encounter at from enf v1 to display second line after app update while risk level calc is not finished * fixed di * fixed tests * fixed tests * fixed tests * Add unit tests for DownloadDiagnosisKeysTask.kt * fixed tests * Add tests for DownloadDiagnosisKeysSettingsTest Co-authored-by:
Matthias Urhahn <matthias.urhahn@sap.com>
-
- Dec 02, 2020
-
-
chris-cwa authored
* fixed: tasks are run, even if preconditions not met * test * test * test * Adjust test for preconditions. * Add task state logging messages. Co-authored-by:
Matthias Urhahn <matthias.urhahn@sap.com>
-
Matthias Urhahn authored
- Dec 01, 2020
-
-
Matthias Urhahn authored
* Remove "lastTimeDiagnosisKeysFromServerFetch" and replace it with less missleading data. While it was called "lastTimeDiagnosisKeysFromServerFetch" it was actually "last time we submitted keys to google". * To decide whether to refresh in "onResume", we now use "has there been any submission to the ENF?" * To display a timestamp on the risk card, we take the last successful submission to the ENF as the risk card displays the calculation results based on the latest submission. While we could use the last calculated risk level result timestamp, we currently also trigger risk calculations if there are no new submissions to the ENF, which would mean the timestamp is updated even though the result is not based on new data. I've also fixed the test fragment button behavior and added descriptions, the "Reset risk level" button surfaced the initial issue because it behaved like a "do a 75% data reset" button. * Tests and LINTs Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com> Co-authored-by:
Ralf Gehrer <ralfgehrer@users.noreply.github.com>
-
Matthias Urhahn authored
Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
Matthias Urhahn authored
* Don't show last risk contact when tracing is disabled. * Add unit test. Co-authored-by:
Ralf Gehrer <ralfgehrer@users.noreply.github.com>
-
Matthias Urhahn authored
- Nov 30, 2020
-
-
Katharina Seiz authored
Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
Ralf Gehrer authored
Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
Matthias Urhahn authored
* Fix displayed details in tracing inactive states. * Simplified UI states. Replaced RiskLevel and RiskLevelConstants with RiskState { LOW; HIGH, FAILED }. * Fix low risk card missing the encounters if there have been more than 0. * Fix missing card divider/border on error cards in light mode. * Fix merge regression. * LINTs * Fix progress card colors on white card background color. * Fix progress card colors on white card background color. * Don't allow negative active tracing days. * Revert sync behavior (extra PR) * Address PR comments. Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
Matthias Urhahn authored
* Remove minimum tracing time requirement. * LINT issues. Co-authored-by:
BMItter <46747780+BMItter@users.noreply.github.com> Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
SAP LX Lab Service Account authored
Change-Id: Ic383ee5f17031502ba2a5b1e0a5f5f2dec23cb48 Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com> Co-authored-by:
Ralf Gehrer <ralfgehrer@users.noreply.github.com>
-
Matthias Urhahn authored
Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
chris-cwa authored
Low Risk after update from 1.7.0 RC8 (in increased risk state) to 1.8.0 RC2 (EXPOSUREAPP-3988) (#1745) * check whether there already is a v2 exposure * check preconditions when selecting task for execution - not when scheduling it * fixed tests * fixed detekt * removed todo that was already addressed by d4rken * updated tests * https://github.com/corona-warn-app/cwa-app-android/pull/1745#discussion_r532568615 Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com> Co-authored-by:
Matthias Urhahn <matthias.urhahn@sap.com>
-
Matthias Urhahn authored
* Add missing RiskLevelStorage reset call when using the internal app reset functionality. * Improve TaskController logging. * Use the day/hour of the last key package download to determine whether the key pkgs are outdated when calculating the risk level. Co-authored-by:
BMItter <46747780+BMItter@users.noreply.github.com> Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
Matthias Urhahn authored
* Adding missing log tags, otherwise displays "BaseContinuationImpl" etc. * Remember the last risk level result for which we did a change check. This fixed the issue that if no new risk level calculation happened, and the last one triggered a notification, killing and restarting the app would also trigger a notification. Co-authored-by:
Ralf Gehrer <ralfgehrer@users.noreply.github.com> Co-authored-by:
BMItter <46747780+BMItter@users.noreply.github.com>
-
Matthias Urhahn authored
Co-authored-by:
BMItter <46747780+BMItter@users.noreply.github.com>
-
Maximilian Lenkeit authored
* Adopt Exposure Window test cases to new TRL encoding keys with report type RECURSIVE are dropped by Android in Exposure Window mode. The new encoding uses RECUSRIVE only with TRL 1 and 2 which are dropped anyway. https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-4039 * Adopt default App Config to new TRL encoding keys with report type RECURSIVE are dropped by Android in Exposure Window mode. The new encoding uses RECUSRIVE only with TRL 1 and 2 which are dropped anyway. https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-4039 https://github.com/corona-warn-app/cwa-protocol-buffers/commit/634c13c687a8f84d737a23c84e0e7c86e8e8bf9d Co-authored-by:
BMItter <46747780+BMItter@users.noreply.github.com>
-
Matthias Urhahn authored
# Conflicts: # Corona-Warn-App/src/main/java/de/rki/coronawarnapp/notification/NotificationHelper.kt # Corona-Warn-App/src/main/java/de/rki/coronawarnapp/risk/DefaultRiskLevels.kt # Corona-Warn-App/src/main/java/de/rki/coronawarnapp/worker/BackgroundWorkHelper.kt # Corona-Warn-App/src/main/java/de/rki/coronawarnapp/worker/DiagnosisTestResultRetrievalPeriodicWorker.kt # gradle.properties
-
Matthias Urhahn authored
Co-authored-by:
Chilja Gossow <49635654+chiljamgossow@users.noreply.github.com>
-
Chilja Gossow authored
* Extract native libs set to true for both builds (DEV) (#1689) * Fix sporadic worker crash on older android versions (EXPOSUREAPP-3987) (#1727) * Fix notification issues by introducing IDs (EXPOSUREAPP-3971) (#1732) * Reduce redundant code in notifications and introduce notification IDs * Clean up unused constants * Cancel risk score level notification once new test result is available * Add more logging Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com> * Versionbump for 1.7.1/RC1 (DEV) (#1733) Co-authored-by:
Katharina Seiz <Katharina.Seiz@sap.com> Co-authored-by:
AlexanderAlferov <64849422+AlexanderAlferov@users.noreply.github.com> Co-authored-by:
Matthias Urhahn <matthias.urhahn@sap.com> Co-authored-by:
Ralf Gehrer <ralfgehrer@users.noreply.github.com> Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
Matthias Urhahn authored
-
- Nov 27, 2020
-
-
BMItter authored
* Use lastRiskResult from DB * use correct format for windows and timestamp * klint * Reduce RiskLevelResult Storage API and fill exposure windows in risk result if available. * Default exposure windows to null while mapping * Don't add empty exposure windows list to risk results * fix broken tests * Added tests for exposure windows Co-authored-by:
Matthias Urhahn <matthias.urhahn@sap.com>
-
chris-cwa authored
-
- Nov 26, 2020
-
-
Kolya Opahle authored
* Converted ExposureWindows to their json wrapper counterparts before exporting to give the json fields proper names instead of the obfuscated enf ones Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * Added timestamp to exposure window export * Switched to a more file name compatible DateTimeFormat Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * ktlint says these are redundant, i don't like it but the overlords forced me to do it. Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * changed filename suffix to json Co-authored-by:
BMItter <berndus@gmx.de>
-
Ralf Gehrer authored
* Reduce redundant code in notifications and introduce notification IDs * Clean up unused constants * Cancel risk score level notification once new test result is available * Add more logging Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
Matthias Urhahn authored
-
Matthias Urhahn authored
* Update to latest stable coroutines. * Fix flaky test. Depending how how fast items emitted, some intermediate values might never be emitted.
-
- Nov 25, 2020
-
-
Alex Paulescu authored
* Removed traces of grey risk card. * Removed UNKNOWN_RISK_INITIAL constant. * Removed unused method. * Removed old comments. * Introduce risklevel calculation failure state to get consistent card states. * Cleaned up the risk card states. Refactored "RiskLevel" to be calculated based on either result or failure reasons. Added the new "no internet" error card. * Updated color states. * Fixed card color issues. * Fixed detekt issues. * Remove test for deleted file. * Fix test regressions. * Fixed tests and LINTs. Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com> Co-authored-by:
Matthias Urhahn <matthias.urhahn@sap.com>
-
Katharina Seiz authored
-
Ralf Gehrer authored
* [INTERNAL] Translation delivery: commit by LX Lab Change-Id: I87af5066f13b8b4ca0c120cc19f5b48e0f2f05b5 * Update default translations Co-authored-by:
service-tip-git <tmsatsls+github.com_service-tip-git@sap.com> Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com>
-
Kolya Opahle authored
Risk Calculation does not work because DiagnosisKeysDataMapping is not applied (EXPOSUREAPP-3895) (#1690) * We now check for the DiagnosisKeyDataMapping and apply it to the ENFClient if changed Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * Moved diagnosisKeysDataMapping to windowProvider Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * Renaming and linting Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * Moved app config fetch to key provide task, added error handling, added logging to config replace Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * Fixed old unit tests and implemented tests for config comparison, TestForAPIFragment is currently broken Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * Linting * Added more unit testing for DefaultDiagnosisKeysDataMapper and fixed TestForAPIFragment Signed-off-by:
Kolya Opahle <k.opahle@sap.com> * Update default app config to latest version This includes a change for the default for reportTypeWhenMissing from 0 to 1, as 0 is not accepted by setDiagnosisKeysDataMapping. https://github.com/corona-warn-app/cwa-app-tech-spec/pull/10/commits/090801921f4a8581543a9f716fd0572c12901c71 https://github.com/corona-warn-app/cwa-protocol-buffers/commit/38a641e2a808c41d225e9fd09d27ec7959551412 * Fixed Unittests Co-authored-by:
Maximilian Lenkeit <maximilian.lenkeit@sap.com> Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com> Co-authored-by:
Ralf Gehrer <ralfgehrer@users.noreply.github.com>
-
Matthias Urhahn authored
Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com> Co-authored-by:
Ralf Gehrer <ralfgehrer@users.noreply.github.com>
-
Matthias Urhahn authored
* Check whether the local config file exists before parsing it. * Force types deserialized via Gson to be non-null. Perform sanity checks and empty file deletion directly when trying to load the json file. * Check that empty json file is deleted. * LINTs * Test parsing exception. Co-authored-by:
Kolya Opahle <k.opahle@sap.com> Co-authored-by:
harambasicluka <64483219+harambasicluka@users.noreply.github.com> Co-authored-by:
Ralf Gehrer <ralfgehrer@users.noreply.github.com>
-
Kolya Opahle authored
Screen: Andere warnen --> Button Einverstanden greyed out (EXPOSUREAPP-3770)
-