mirror of
https://github.com/permissionlesstech/bitchat-android.git
synced 2026-10-18 07:33:01 +00:00
b79ae8e7f1
the rate limit that triggers the gate Addresses review on #812. The awaiting-route phase was never cleared. Reporting it before the wait fixed the label on the wait itself, but nothing restored ResolvingRelease afterwards, so the UI and notification claimed "Waiting for Tor" for the whole metadata request and its retries -- and in direct mode, where the wait returns immediately, for a wait that never happened. An onResolvingRelease callback now fires once the route is ready. A rate-limit rejection recorded the gate and returned the failure, while the stale-cache fallback sat at the top of the function and was only reached on a later call. The first About check therefore reported an error the user could not act on, and an immediate retry succeeded from metadata that was already present. The response that sets the gate now serves the cached release straight away. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>