Go to file
Honza Rychnovsky adc774a20d
[#313] scan qr screen functional
* [#312] [#309] Scaffold Scan QR Screen
- Screen scaffolding.
- Model classes.
- Screen states handling.
- Needed dependencies added.
- Camera permission handling. Redirect to Settings.
- Added SettingsUtilTest class.
- Added view classes tests.
- Renamed tag class in update package.
- Fix the scan frame size while changing the screen orientation.
- Use local variable for cameraProvider.
- Use UUID for source of randomness.
- Eliminate blocking call for camera.
- Fix preview name.
- Remove Google Guava dependency.
- Suppress Lint warning.
- Improved calculation of the camera frame size. Moved it into Constraint layout.
- Added custom image analyser class.
- Implemented logic for the QR scan screen while QR code is found.
- Manual tests added.
- New module with integration tests for QR Scan screen. Added 3 integration and 4 view tests.
- Simplify QR Scan screen view basic tests.
- Switched from pure compose permission handling to Accompanist way of handling CAMERA permission.
- Added validation of Zcash wallet address from QR scanning result.
- Fix the integration tests for the CI WTF emulator runs.
- Add comment on RTL test result.
- Improve waitForDeviceIdle() method. Use it on the other test too.
- Change the integration test module main manifest package name.
- Debounce scans.
- Improve thread safety of scan collection.
- Added instructions on how to set up an emulator in manual tests.
- Replace compose collectAsState() with coroutine launch().
- Add sample() to get rid of several callback events at the same time.
- Stop updating the scanState when it's already in Scanning state.
- Fix condition on navigation.
- Remove validateJob check.
- Speed up the integration test
- Wrap ImageAnalysis.qrCodeFlow to remember.
- Auto-close the camera image when we're done with it in all cases.
- Update minimal SDK version to 24 for WTF emulators.
- Update Architecture documentation.
- Removed extra blank space in ui-design module definition.
- Add ui-integration-test-lib.
- Update Mermaid diagram with newly added module.
- Move UI modules into one wrap in the diagram.
- Move sdk-ext-lib and sdk-ext-ui under the same modules section.
- Update camera dependencies.
Co-authored-by: Carter Jernigan <git@carterjernigan.com>
2022-06-02 13:35:51 +02:00
.github [#456] GitHub Cache Action 3.0.3 2022-06-01 05:22:57 -04:00
.idea [#303] Write crash logs on external storage (#429) 2022-05-31 12:38:02 -04:00
app [#303] Write crash logs on external storage (#429) 2022-05-31 12:38:02 -04:00
build-convention [#313] scan qr screen functional 2022-06-02 13:35:51 +02:00
build-info-lib [#421] Kotlin 1.6.21 and Compose Compiler 1.2.0-beta02 2022-06-01 05:22:57 -04:00
buildSrc [#297] Add locking to buildSrc and build-conventions 2022-04-06 07:56:17 -04:00
crash-android-lib [#303] Write crash logs on external storage (#429) 2022-05-31 12:38:02 -04:00
crash-lib [#460] Coroutines 1.6.2 2022-06-01 05:22:57 -04:00
docs [#313] scan qr screen functional 2022-06-02 13:35:51 +02:00
gradle/wrapper [#302] Gradle 7.4.2 2022-04-06 07:56:17 -04:00
preference-api-lib [#460] Coroutines 1.6.2 2022-06-01 05:22:57 -04:00
preference-impl-android-lib [#303] Write crash logs on external storage (#429) 2022-05-31 12:38:02 -04:00
sdk-ext-lib [#303] Write crash logs on external storage (#429) 2022-05-31 12:38:02 -04:00
sdk-ext-ui-lib [#303] Write crash logs on external storage (#429) 2022-05-31 12:38:02 -04:00
spackle-android-lib [#303] Write crash logs on external storage (#429) 2022-05-31 12:38:02 -04:00
spackle-lib [#460] Coroutines 1.6.2 2022-06-01 05:22:57 -04:00
test-lib [#6] Refactor kotlinOptions to build-conventions 2022-05-17 06:06:44 -04:00
tools [#387] Detekt 1.20.0 2022-06-01 05:22:57 -04:00
ui-design-lib [#303] Write crash logs on external storage (#429) 2022-05-31 12:38:02 -04:00
ui-integration-test-lib [#313] scan qr screen functional 2022-06-02 13:35:51 +02:00
ui-lib [#313] scan qr screen functional 2022-06-02 13:35:51 +02:00
.gitignore [#50] Preliminary design guide 2021-10-31 13:36:51 -04:00
LICENSE Initial commit 2021-07-29 13:54:16 -04:00
README.md [#431] Switch to Adoptium JDK 2022-05-17 06:07:22 -04:00
build.gradle.kts [#190] Pull screenshots on CI 2022-05-24 09:39:56 -04:00
buildscript-gradle.lockfile [#421] Kotlin 1.6.21 and Compose Compiler 1.2.0-beta02 2022-06-01 05:22:57 -04:00
gradle.properties [#313] scan qr screen functional 2022-06-02 13:35:51 +02:00
gradlew [#3] Add skeleton Gradle project structure 2021-09-18 07:22:42 -04:00
gradlew.bat [#3] Add skeleton Gradle project structure 2021-09-18 07:22:42 -04:00
settings.gradle.kts [#313] scan qr screen functional 2022-06-02 13:35:51 +02:00

README.md

secant-android-wallet

Note: As of September 2021, this is a brand new project. Since it is being developed in the open from the beginning, initially this project will not be fully functional. Some of the documentation below will be aspirational until the implementation is further along. During this initial stage of development, the older Zcash Android Wallet may be a more helpful sample.

This is a sample implementation of a Zcash wallet for Android leveraging the Zcash Android SDK. The goal is to exercise the SDK and related Zcash libraries, as well as demonstrate how the SDK works.

While we aim to continue improving this sample, it is not an official product. We open sourced it as a resource to make wallet development easier for the Zcash ecosystem.

Getting Started

If you'd like to compile this application from source, please see our Setup Documentation to get started.

Reporting an issue

If you wish to report a security issue, please follow our Responsible Disclosure guidelines. See the Wallet App Threat Model for more information about the security and privacy limitations of the wallet.

If you'd like to report a technical issue or feature request for the Android Wallet, please file a GitHub issue.

General Zcash questions and/or support requests and are best directed to either:

Contributing

Contributions are very much welcomed! Please read our Contributing Guidelines to learn about our process.

Forking

If you plan to fork the project to create a new app of your own, please make the following changes. (If you're making a GitHub fork to contribute back to the project, these steps are not necessary.)

  1. Change the app name under app/src/main/res/values/strings.xml
  2. Change the support email address under ui-lib/src/res/ui/support/values/strings.xml
  3. Remove any copyrighted ZCash or Electric Coin Company icons, logos, or assets
    1. ui-lib/src/main/res/common/ - All of the the ic_launcher assets
  4. Change the package name
    1. Under app/build.gradle.kts, change the package name of the application
  5. Optional
    1. Configure secrets for Continuous Integration.

Known Issues

  1. During builds, a warning will be printed that says "Unable to detect AGP versions for included builds. All projects in the build should use the same AGP version." This can be safely ignored. The version under build-conventions is the same as the version used elsewhere in the application.
  2. When the code coverage Gradle property IS_COVERAGE_ENABLED is enabled, the debug app APK cannot be run. The coverage flag should therefore only be set when running automated tests.
  3. Test coverage for Compose code will be low, due to known limitations in the interaction between Compose and Jacoco.
  4. Adding the espresso-contrib dependency will cause builds to fail, due to conflicting classes. This is a known issue with the Zcash Android SDK.
  5. Android Studio will warn about the Gradle checksum. This is a known issue and can be safely ignored.
  6. #96 - Release builds print some R8 warnings which can be safely ignored.
  7. During app first launch, the following exception starting with AndroidKeysetManager: keyset not found, will generate a new one is printed twice. This exception is not an error, and the code is not being invoked twice.
  8. When running instrumentation tests for the app module, this warning will be printed WARNING: Failed to retrieve additional test outputs from device. com.android.ddmlib.SyncException: Remote object doesn't exist! followed by a stacktrace. This can be safely ignored.