Claude 54863e37dc Start app immediately, wait for Tor only before connecting ...

Previously runMigrations() blocked the entire app startup (and UI) waiting
for the built-in Tor daemon to come online. This moves the startup gate so:

- TorManager.start() is called immediately at migration start
- isStartingApp is set to false right after the lifecycle observer is
  registered, so the UI becomes visible without waiting for Tor
- The Tor readiness wait (with retry logic) is kept but now happens *after*
  isStartingApp=false, delaying only relay connections
- ConnectivityService.waitForTorIfNeeded() is called after the startup gate
  so it also holds off on client.connect() until Tor is ready
- A new Amber.waitForTorIfNeeded() helper encapsulates the TorManager check

https://claude.ai/code/session_01QfnSvDcaWayKwrAM71QUeA

2026-03-18 09:00:12 +00:00

..

release

add more event descriptions

2024-03-01 06:56:32 -03:00

schemas

Add database schema version 17 and extend AmberEvent relay helper

2026-03-09 07:56:17 -03:00

src

Start app immediately, wait for Tor only before connecting

2026-03-18 09:00:12 +00:00

.gitignore

init

2023-07-26 16:44:33 -03:00

build.gradle

Revert okhttp/coil to implementation; rely on manifest remove for offline

2026-03-16 19:39:22 +00:00

proguard-rules.pro

Update ProGuard rules to suppress ErrorProne warnings

2026-01-30 05:30:33 -03:00