ReactorcoremeltdownandClaude Opus 5.5
318bd68908
The Android app kept a pending browser sign-in in a thread inside the login screen. Android often kills the process while the browser is in front, so the approval reached the server but nothing collected it, and the app came back signed out with nothing saved. The pending device code is now kept in Prefs and collected whenever the login screen resumes. The app passes return_url=keeporg://device-approved when it starts the sign-in, and the server's approval page, after a password or single sign-on, links back to it. Only the keeporg: scheme is accepted. Against a server older than 0.9, which rejects the field, the app retries without it. Verified on an Android 15 emulator: approval collected after the process was killed, and the fallback against the 0.8 server. Server 0.9.0, Android 0.3.0 (versionCode 3). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
KeepOrg for Android
A KDBX synchronization adapter with no third-party dependencies: the server
is reached with java.net.HttpURLConnection, JSON is parsed with the
platform's org.json, and the two screens are built in code. The release APK
is about 650 KB.
How a KeePass application sees it
KeepOrgProvider is a DocumentsProvider, so the mirrored databases appear
in every file picker under "KeepOrg". KeePassDX and Keepass2Android open them
like any other document. When the application closes a file it had opened for
writing, the provider triggers a synchronization pass, which is how a save
reaches the server.
SyncService is a foreground service that holds the server's event stream
open, so a change pushed by a colleague arrives without opening the app. The
user turns it on from the main screen; it is not started at boot.
Nothing the app holds may leave the device in a backup or a device transfer:
res/xml/data_extraction_rules.xml and res/xml/backup_rules.xml exclude
every domain. The session token authenticates as the user, and the mirrored
files are the organization's password databases.
The merge policy in Mirror.decide is the same table as the desktop client's
internal/client/decide.go. Keep the two in step.
Building
Requirements: JDK 17 (lint in AGP 8.7 fails on newer JDKs; set JAVA_HOME
to a 17 when Gradle defaults to something else), Gradle 8.9 or newer, and an
Android SDK with
platforms;android-35 and build-tools;35.0.0.
export ANDROID_HOME=$HOME/android-sdk
make android # unsigned release APK, named for the F-Droid repository
make android-lint # lint; the project is kept at zero findings
make android-publish
The Gradle wrapper is not committed, so the Makefile calls whichever gradle
is on PATH. Generate a wrapper if you prefer one:
gradle wrapper --gradle-version 8.10.2.
The release build is deliberately unsigned: the private F-Droid repository signs what it publishes.
Building on an arm64 Linux host
Google ships aapt2 for linux-x86_64 only, so an aarch64 build host needs to
be able to run it. Debian's own arm64 aapt2 is too old to read the API 35
android.jar, so run the official one through QEMU instead:
sudo dpkg --add-architecture amd64
sudo apt update
sudo apt install qemu-user-static libc6:amd64 libstdc++6:amd64 zlib1g:amd64
After that aapt2 runs transparently and the build needs no further flags.
Everything else in the Android toolchain (R8, the resource merger, zipflinger,
apksig) is Java and architecture-independent.
What is verified and what is not
The APK builds clean and lint reports no issues, and the packaged DEX contains every class the manifest names. The app has not been exercised on a device or emulator: there was none available. The first real run is where to confirm the picker integration, the save-triggered sync and the notification.