You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
android: plain close of Settings at replay teardown fails intermittently after #4881 #4895
failed at: Android app com.android.settings process remained running after close
Seen twice on 2026-11-21 on PRs based on 0.22 after it picked up #4881 (plain close and .ad script teardown now close the session app with the Android close fences):
Neither PR touches Android close. The same base passed on #4857 and #4869.
Likely cause: Android can restart Settings at once after force-stop (see the close docs: apps Android restarts at once fail with details.phase: process). Before #4881, a script that ended with plain close did not close the app, so the fence never ran on Settings at teardown. Now the fence runs and can fail on a restart that is not caused by the script.
Decide whether teardown close (and plain close without an app) should accept a restarted process the way open --relaunch does, or whether the fixture should close a different app.
The issue reports a reproducible intermittent Android smoke test failure caused by plain close teardown after #4881, where Settings can restart and make the close fence fail. It includes failing test, error message, PRs, links, and likely cause, so a maintainer can investigate and decide the close/teardown behavior.
Fixed by #4902 on main (ffef4b7), cherry-picked into 0.22 as b656532: close now succeeds once the pre-close processes are gone, so a Settings restart after the stop no longer fails the replay teardown. Duplicate of #4901.
Activity
apex-sentinel-staging commentedon Nov 21, 2026
Apex Sentinel · Issue review
Suggested label:
bugThe issue reports a reproducible intermittent Android smoke test failure caused by plain close teardown after #4881, where Settings can restart and make the close fence fail. It includes failing test, error message, PRs, links, and likely cause, so a maintainer can investigate and decide the close/teardown behavior.
Required sections
thymikee commentedon Nov 21, 2026
Another sighting: #4911 at b414200, job https://github.com/callstack/agent-device/actions/runs/44925693984/job/136911155109. The same test passed on that PR's previous head 93a810c, and the change between the two heads does not touch Android or close. Also seen today on runs 44916960661, 44913451859 and 44913308426 (other branches).
thymikee commentedon Nov 21, 2026
Fixed by #4902 on main (ffef4b7), cherry-picked into 0.22 as b656532: close now succeeds once the pre-close processes are gone, so a Settings restart after the stop no longer fails the replay teardown. Duplicate of #4901.