Skip to content
Snippets Groups Projects
Select Git revision
  • main default protected
  • changes-try-with-http
  • changes
  • feature/10632-check-in-for-2g-events
  • feature/10535-luca
  • fix/10609-crash-in-booster-rules-test-menu
  • release/2.16.x
  • release/2.15.x
  • fix/delete-duplicate-ids
  • fix/11016-max-limit
  • feature/10888-2g-events-person-overview-ui-changes
  • feature/10698-advanced-root-warning
  • fix/allowlist-navigation-issue
  • feature/10887-Determining_admission_state
  • Wrong-title-on-screen-Zertifikat-auswählen
  • feature/10738-http-logging
  • feature/10644-consent-navigation
  • feature/10635-certificate-pinning
  • feature/10651-selection-consent-II-skeleton
  • release/2.14.x
  • v2.15.1-RC2
  • v2.15.1-RC1
  • v2.15.1-RC0
  • v2.15.0-RC2
  • v2.15.0-RC1
  • v2.15.0-RC0
  • v2.14.1
  • v2.14.1-RC1
  • v2.14.1-RC0
  • v2.14.0-RC1
  • v2.13.3
  • v2.13.3-RC2
  • v2.13.3-RC1
  • v2.13.3-RC0
  • v2.13.2
  • v2.13.2-RC0
  • v2.14.0-RC0
  • v2.13.1
  • v2.13.1-RC1
  • v2.13.1-RC0
40 results
Compare
user avatar
Parse test JSON files and init unit tests with respective parameters (EXPOSUREAPP-3456) (#1575)
AlexanderAlferov authored 
* Split and hide the protobuf config behind interfaces with individual mappers responsible for creating the desired formats.

* Merge branch 'release/1.7.x' into feature/3455-more-frequent-riskscore-updates-configs

# Conflicts:
#	Corona-Warn-App/src/deviceForTesters/java/de/rki/coronawarnapp/test/risklevel/ui/TestRiskLevelCalculationFragmentCWAViewModel.kt
#	Corona-Warn-App/src/main/java/de/rki/coronawarnapp/transaction/RiskLevelTransaction.kt
#	Corona-Warn-App/src/test/java/de/rki/coronawarnapp/transaction/RiskLevelTransactionTest.kt

* Make the AppConfig observable.
Provide the server time offset.
Offer a lastUpdatedAt timestamp.
Add an app config specific test screen.
Clean up test screens a bit and move debug options out of API test options.

* Fix test regression due to refactoring (moved code around).

* Store the server timestamp and offset at retrieval.
Switch to config storage via json to be able to store additional meta data fields (i.e. time).

* KLint and Me have a hate relationship based on both mutual admiration.

* Fix time offset parsing being locale dependent.

* Fix broken unit tests.

* Improve offset accuracy, move before unzipping.

* Fix overly long livedata subscription to results (viewmodel scope vs observer scope)

* Add mapping for the new protobuf configs + tests.

* For cached (retrofit) response, we need to check the cacheResponse and its timestamps
to determine an accurate time offset.

* Exposure a boolean property to tell us when a fallback config is being used.

* Hide the observable flow<ConfigData> behind a method that can automatically triggers refreshes.

* Use a common mapper interface.

* set old risklevelcalculation deprecated

* Created skeleton for new risk calculation and aggregation

* Initial

* Implementing steps to aggregate results form exposure windows - wip

* Address PR comments and KLints.

* Fix refactoring regression.

* ktlint

* Json parsing

* Added ExposureWindowRiskLevelConfig and ExposureWindowRiskLevelConfigMapper for new config api (not yet introduced)

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

* Added first Implementation of exposure window based calculateRisk function

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

* Added generics to Range.inRange

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

* Added Ugly Hack to RiskLevelTransaction to allow for compilation during testing

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

* Linting and injecting RiskLevelCalculation into TestRiskLevelCalculationFragmentCWAViewModel, currently wont build because ExposureWindowRiskLevelConfig has no Provider

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

* Linting extravaganza

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

* Lint Wars Episode VI: Return of the trailing Comma

* Improve config unzipping code.

* Add flag to forward exception thrown during HotDataFlow.kt initialization.

* Don't specify a default context via singleton.

* Move download and fallback logic into it's own class just responsible for sourcing the config: "AppConfigSource".
"AppConfigProvider" is now only responsible for making it available.

* Check test cases

* Simplify current concepts for making the app config observable until we have a default configuration.

* Implementing steps to aggregate results form exposure windows

* cleaned todo

* Adjusted default values

* Improve app config test screen, delete options, better feedback.
Show toast instead of crash on errors.

* Fixed GSON serialization not encoding/decoding the byte array correctly.
Added specific type adapters for instant and duration to get cleaner json.

* Remove type adapters from base gson due to conflict with CalculationTrackerStorage.

* refactored Windows aggregation

* We want to default to forced serialization of instant by our converters, instead of using the default serialization which will differ
between Java8.Instant and JodaTime.Instant, to prevent future headaches there, register explicit converters by default,
and overwrite them if necessary (currently only needed for CalculationTrackerStorage.kt).

* Improve AppConfigServer code readability by moving code into extensions.

* Fix merge conflicts

* removed example value

* Added missing import to WorkerBinderTest

* fixed unit tests

* Removed auto formatting on unrelated files (revert + cherry pick in other commit)

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

* Implementing steps to aggregate results form exposure windows

* Renamed ExposureWindowRiskLevelConfig to ExposureWindowRiskCalculationConfig

* adjusted & refactored Windows aggregation

* removed example Values

* satisfy lint

* make Aggregation work with Instant now

* Use long while calculation

* Added normalizedTimePerDayToRiskLevelMappingList to AppConfig

* normalizedTimePerDayToRiskLevelMappingList from AppConfig

* satisfy lint

* Get AppConfig on init and listen for updates

* exposureData to aggregatedRiskPerDateResult

* Corrected name in ConfigParserTest

* use instant for specific aggregation logs

* satisfy CI

* satisfy detekt

* Mock exposure windows

* Full test process

* Fix gitignore

* Improved logging

* Correct test cases dates handling

* Config fix and logs

* Small clean up

* fixed some naming and conversion issues with json test case parsing

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

* TRL Encodings in config did not match TRL Encodings used in js example

* Removing a return that broke the calculation

* Actual tests and formatting

* Formatting

Co-authored-by: default avatarMatthias Urhahn <matthias.urhahn@sap.com>
Co-authored-by: default avatarBMItter <Berndus@gmx.de>
Co-authored-by: default avatarKolya Opahle <k.opahle@sap.com>
Co-authored-by: default avatarharambasicluka <64483219+harambasicluka@users.noreply.github.com>
3687be81
History
user avatar 3687be81
History
Name Last commit Last update
.circleci
.github
.idea/codeStyles
.pipeline
Corona-Warn-App
Server-Protocol-Buffer
docs
gradle/wrapper
protobuf/build
.editorconfig
.gitignore
CODEOWNERS
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
NOTICE
README.md
SECURITY.md
THIRD-PARTY-NOTICES
build.gradle
gradle.properties
gradlew
gradlew.bat
prod_environments.json
settings.gradle
sonar-project.properties
translation_v2.json
README.md

Corona Warn App - Android

Development • Documentation • Contribute • Support • Changelog • Licensing

The goal of this project is to develop the official Corona-Warn-App for Germany based on the exposure notification API from Apple and Google. The apps (for both iOS and Android) use Bluetooth technology to exchange anonymous encrypted data with other mobile phones (on which the app is also installed) in the vicinity of an app user's phone. The data is stored locally on each user's device, preventing authorities or other parties from accessing or controlling the data. This repository contains the native Android implementation of the Corona-Warn-App. Visit our FAQ page for more information and common issues

Development

Known Issues

  • The Exposure Notification API is going to block you from successfully testing the Application unless you are whitelisted inside GMS; Shoutout to @pocmo for working on a demo mode to test unreleased app versions in advance without whitelisting (issue #321), if you want to contribute you can reach out here for the time being - thank you!
  • The Storage is currently based on Encrypted Shared Preferences and SQL Cipher (SQLite) - this could change in the future
  • Test Coverage is generally low and needs to be improved. We appreciate your help here!
  • In General every TODO comment within the code or the documentation can be regarded as an issue. You are free to tackle the TODOs anytime!
  • We are aware of the Play Store Limitations of GMS.
  • Without your own server instance (e.g. a local Docker setup), you will not be able to test the Application. For help, please refer to the server implementation.
  • Strings including translations are handled separately, for suggestions / findings please have a look at issue #332

Architecture & Documentation

The full documentation for the Corona-Warn-App is in the cwa-documentation repository. The documentation repository contains technical documents, architecture information, UI/UX specifications, and whitepapers related to this implementation.

Support & Feedback

The following channels are available for discussions, feedback, and support requests:

Type Channel
General Discussion
Feature Requests
Concept Feedback
Android App Issue
Backend Issue
Other Requests

How to Contribute

Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines. By participating in this project, you agree to abide by its Code of Conduct at all times.

Contributors

The German government has asked SAP and Deutsche Telekom to develop the Corona-Warn-App for Germany as open source software. Deutsche Telekom is providing the network and mobile technology and will operate and run the backend for the app in a safe, scalable and stable manner. SAP is responsible for the app development, its framework and the underlying platform. Therefore, development teams of SAP and Deutsche Telekom are contributing to this project. At the same time our commitment to open source means that we are enabling -in fact encouraging- all interested parties to contribute and become part of its developer community.

Repositories

Repository Description
cwa-documentation Project overview, general documentation, and white papers.
cwa-wishlist Community feature requests.
cwa-app-ios Native iOS app using the Apple/Google exposure notification API.
cwa-app-android Native Android app using the Apple/Google exposure notification API.
cwa-server Backend implementation for the Apple/Google exposure notification API.
cwa-verification-server Backend implementation of the verification process.

Licensing

Copyright (c) 2020 SAP SE or an SAP affiliate company.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.

You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the LICENSE for the specific language governing permissions and limitations under the License.