docs: record verified Android login fix artifact and regression results
Android validation / emulator (35) (push) Failing after 4s
Android validation / emulator (37.0) (push) Failing after 4s
iOS validation / simulator (push) Successful in 1m4s
Android validation / build (push) Successful in 5m45s

This commit is contained in:
Yuvomi Mobile Contributors committed 2026-10-21 10:00:28 +02:00
1 parent 4b483c20e3
commit bd0e4cc4fb
3 files changed
+27 -1

No files matched your search

+14 -1
View File
@@ -27,8 +27,21 @@ and session-only cookie persistence remain disallowed.
error, native dashboard/recreation, task/note/shopping calls and logout.
- 13 JVM tests passed, including default-cookie persistence/deletion, expired/empty
session detection and separate credential/2FA/session-handoff error messages.
- Both lint variants, debug/unsigned release APK/AAB builds and the 6-test ordinary
native UI suite passed. Its first attempt hit a leftover CI-debug certificate
mismatch and produced zero tests; the verifier correctly rejected it. After
confirming the fixture package was absent, the rerun executed all 6 with no
failures/skips (`/home/neste/yuvomi-login-debug-retry.log`).
- Logs: `/home/neste/yuvomi-login-cookie-after.log`,
`/home/neste/yuvomi-login-secure-after.log`, `/home/neste/yuvomi-login-unit.log`.
`/home/neste/yuvomi-login-secure-after.log`, `/home/neste/yuvomi-login-unit.log`,
`/home/neste/yuvomi-login-validation.log`.
- Gitea run #11/global 666, build job 1071 at `4b483c2`: packages, JVM/lint,
repository/script/format checks, OSV and artifact uploads all succeeded.
- [Download fixed Android 0.2.1/code 3](https://git.nesterovic.cc/nessi/Yuvomi-App/actions/runs/666/artifacts/android-native-debug-apk).
The ZIP was downloaded and its sole APK version/v2 signature checked; it was
installed and launched on the authorized local emulator. APK SHA-256:
`a769118f0bd16988f76a8ee95c0aa0c5e248104e8ea529eee2e0c83d78b6ca5a`.
This does not certify the still-blocked remote emulator matrix or Apple pipeline.
See [login troubleshooting](login-troubleshooting.md). This reproduces a matching
compatibility defect without accessing the user's server or credentials; it does