SHA256
docs: record verified Android login fix artifact and regression results
This commit is contained in:
1 parent
4b483c20e3
commit
bd0e4cc4fb
3 files changed
+27
-1
No files matched your search
@@ -24,6 +24,14 @@ certificate checks, redirect refusal, encryption and expiry are unchanged. Login
|
||||
errors now distinguish credential/code rejection from session-cookie problems and
|
||||
a successful retry clears the old error. Both secure/default-cookie test modes
|
||||
are in CI; see `login-troubleshooting.md` and the latest validation section.
|
||||
The fix is source `4b483c2`; local 13 JVM, both 7-test cookie modes, 6 ordinary
|
||||
native UI tests, lint and all packages pass. Gitea build job 1071/run 666 (#11)
|
||||
passed and published the actual 0.2.1/code-3 APK; downloaded, verified and installed/
|
||||
launched on `emulator-5554`. Exact link/checksum are in `validation.md`.
|
||||
That CI-signed debug APK is now installed on the local emulator. Its certificate
|
||||
differs from the local Gradle debug key: before another local device-test run,
|
||||
remove only this synthetic preview package or use a fresh AVD. An install failure
|
||||
with zero tests must not be reported as a passing instrumentation run.
|
||||
|
||||
The owner-authorized signing key and four Gitea secrets were created before this
|
||||
correction. Their private backup is `/home/neste/yuvomi-signing/initial-20261021`.
|
||||
|
||||
Reference in new issue
Block a user