Closed ignoramous closed 1 month ago
This behavior is expected to happen on debug builds,
When the app in debug mode, the system can force-stop and restart it to ensure it runs with proper debug hooks attached
.
The system wants to ensure the app is restarted properly in a debug context, so it force-stops the app and relaunches it to ensure all debugging options (like breakpoints, logs, etc.) are initialized correctly.
ref: https://stackoverflow.com/questions/60569758/android-studio-debugger-stops-unexpectedly, https://developer.android.com/studio/debug, https://stackoverflow.com/questions/40618803/android-app-crashes-when-launched-in-debug-mode
From prior logs it looks like this kill happened just before the Settings app's developer options was opened:
From ActivityManager's code (am:resolveActivity), it looks like if an app is sent an intent with
START_FLAG_DEBUG
set (am:setDebugApp), the app is force stopped.The question is, why does it happen with Rethink? Probably only happens on debuggable builds?