feat: android e2e tests

[limpbrains]

Description

• detox e2e tests are running on ubuntu-latest
• had to patch react-native-quick-crypto to make it compile
• updated react-native-camera-kit for the same reason - fix compile error

Type of change

Refactoring

Tests

Detox test

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

[pwltr]

Not sure if that fixes it but according to docs waitFor must have a withTimeout otherwise it doesn't do anything.

Suggested change

	await waitFor(element(by.id('NewWallet'))).toBeVisible();
	await sleep(100); // wtf?
	await waitFor(element(by.id('NewWallet'))).toBeVisible().withTimeout(2000);
	await sleep(100); // wtf?

https://github.com/nubank/detox/blob/master/docs/APIRef.waitFor.md

[limpbrains]

This is a link to outdated version of docs from 7 years ago.
I can't find anything like this on wix.github.io
https://wix.github.io/Detox/docs/api/expect

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	311 kB	scarlac

🚮 Removed packages: npm/[email protected]

View full report↗︎

[limpbrains]

Had to push an update, but before that there were a series of 5 uninterrupted successful test runs
And before that around 10

[limpbrains]

wtf

BUILD SUCCESSFUL in 15m 14s
3066 actionable tasks: 3066 executed
After running the build command, Detox could not find your app at the given binary path:
	android/app/build/outputs/apk/release/app-release.apk

[pwltr]

It's probably because of #1992, try changing it to app-x86_64-release.apk or app-x86_64-debug.apk

[limpbrains]

Is it possible only do x86_64 build for detox tests? This might speedup the build/test

[pwltr]

yeah I think like this in detoxrc should work (just add the flag):

$ ./gradlew :app:assembleDebug -PreactNativeArchitectures=x86_64

[catch-21]

Reviewed the tests and CI runs. We can definitely make some improvements such as remvoing hard-coded waits in favour of checking e.g. that backups have succeeded, but it looks stable and the time saving is not worthwhile at this time. LGTM.