Skip to content

v0.2.3 — Exit the host app on close code 4000

Choose a tag to compare

View all tags
@omnidebuglink omnidebuglink released this 07 Sep 16:25
· 4 commits to main since this release
v0.2.3
09645a4

When the server closes the connection with code 4000 (the device token was just claimed by a newer connection), the SDK now terminates the host process (exitProcess(0)) after logging loudly, instead of staying stopped.

  • Reconnecting after a takeover would ping-pong with the servers kicker forever — one token pair belongs to one device seat, so a kicked client must not come back.
  • This is fail-loud by design: a token accidentally shipped in a release build can no longer keep a silent debug channel alive. Gate start() on BuildConfig.DEBUG or remove it from release builds.
  • Normal brief disconnects are unaffected (watchdog-cancelled sockets can never re-enter onClosed; verified against OkHttp 4.12 internals).

Upgrade: bump to v0.2.3 — implementation 'com.github.omnidebuglink:omnidebuglink_android:v0.2.3' (JitPack).

Assets 2
Loading