QRun-IO/qqq-android
3
0 Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases 3 Wiki Activity

WIP: test(e2e): accept the scan fixture's raw bytes as Base64 text #29

Draft
james.maes wants to merge 2 commits from feat/e2e-scan-base64-extra into main
pull from: feat/e2e-scan-base64-extra
merge into: QRun-IO:main
Conversation 0 Commits 2 Files Changed 6
+198 -10
2 Commits
Author SHA1 Message Date
james.maesandClaude Fable 5.2 0419cdea91 test(emu): emulator-only build type with the scan fixture under the normal application ID
android / android (push) Failing after 11m43s
Details
build / android (push) Failing after 11m43s
Details 
A server that registers only the normal scanner callback offers the E2E
package no sign-in, so the fixture could not be used against it. The new
`emu` build type (initWith debug, no applicationIdSuffix, versionNameSuffix
-emu, label "QQQ Mobile EMULATOR TEST") reuses the E2E fixture driver source
under io.qrun.mobile.scanner. It does not take the E2E manifest or network
security config: cleartext stays off and only system trust is used.

Because it carries the normal application ID, the fixture driver is now
created only for the disposable .e2e package (unchanged behaviour) or when
android.os.Build describes an SDK emulator image: HARDWARE goldfish or
ranchu, PRODUCT sdk_*, MODEL sdk_* or "Android SDK built for *", and a
FINGERPRINT naming that same product. Otherwise there is no driver.

Debug, qa and release source sets are unchanged and contain no ingress.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
 2026-11-10 10:48:01 -06:00
james.maesandClaude Fable 5.2 d5c3ac2d6a test(e2e): accept the scan fixture's raw bytes as Base64 text
android / android (push) Failing after 4m0s
Details
build / android (push) Failing after 4m0s
Details 
adb shell am broadcast cannot send a byte-array extra, so a manual emulator
scan could not carry the raw bytes a GS1-128 duplication needs. The E2E
driver now also reads io.qrun.mobile.scanner.e2e.raw_data_base64 (canonical
padded Base64). The byte-array extra still wins when both are present.
Malformed Base64, and an invalid AIM identifier (which used to throw inside
the receiver), now leave the read pending so the broadcast is ignored.

E2E source set only: no change to main, debug, qa, production or release.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
 2026-11-10 10:36:00 -06:00