Inability to successfully terminate com.android.settings on Android 9 (Pie)

Issues/Bugs
1

<selenium.version>3.141.59</selenium.version>
<appium.version>7.0.0</appium.version>
Appium server 1.14.0
The issue cropped up after updating mobile device testing our framework against to Android 9.
Tried again on other devices @ Android 7 & 8 and am not facing the same issue.
We are only testing against Samsung devices.

I have attached the server logs.

The basic test:
start session w/targeting our app to be tested.
androidDriver.activateApp(“com.android.settings”);
androidDriver.terminateApp(“com.android.settings”, new AndroidTerminateApplicationOptions().withTimeout(Duration.ofMillis(10000)));
androidDriver.activateApp(“com.android.settings”);
// The activate/terminate/activate was being used to ensure we started from same settings page location.

The main issue is that I see the settings app being terminated - or the instance we launched - however there seems to be a persistent background settings process that the terminateApp is still witnessing running and rightly throws an exception.

Any ideas?
appiumLog.txt (57.0 KB)

2

Why not set app not allow run in background? It is in app settings.

3

Part of our testing involves pushing the app under test into the background to manipulate say, Power Management modes for the app, location permissions, wifi, bluetooth, etc.

That would also terminate our app which would cause a state change we are trying to avoid.

4

i mean configure it ONLY for ''com.android.settings" app.

5

Mykola suggested the startActivity and indicating the .Settings activity terminates settings then relaunches. This is working for my use-case - though I am wondering if there might be a more appropriate message to send if in later versions of Android behavior such as terminating settings is pre-empted by the OS and not allowed to execute?