"mobile: activateApp" can not work on Honnor V30

[pppppino]

appium version: 2.2.1
driver version: 2.45.1

I try activate app in my python script:
self.driver.execute_script("mobile: activateApp", { "appId": app_id })

I could make sure that my android device have the app with activated app_id (checked by adb shell pm list packages)

But I got this page:

log:

[38;5;0m[HTTP]�[0m �[37m<-- POST /session �[39m�[32m200�[39m �[90m8409 ms - 1251�[39m
�[38;5;0m[HTTP]�[0m �[90m�[39m
�[38;5;0m[HTTP]�[0m �[37m-->�[39m �[37mPOST�[39m �[37m/session/eee974b8-15b0-487d-b1f5-f8ec38b69d5f/execute/sync�[39m
�[38;5;0m[HTTP]�[0m �[90m{"script":"mobile: activateApp","args":[{"appId”:””}]}�[39m
�[38;5;32m[AndroidUiautomator2Driver@2dd1 (eee974b8)]�[0m Calling AppiumDriver.execute() with args: ["mobile: activateApp",[{"appId”:””}],”eee974b8-15b0-487d-b1f5-f8ec38b69d5f"]
�[38;5;32m[AndroidUiautomator2Driver@2dd1 (eee974b8)]�[0m Executing method 'mobile: activateApp'
�[38;5;32m[AndroidUiautomator2Driver@2dd1 (eee974b8)]�[0m Activating ‘**’
�[38;5;48m[ADB]�[0m Running 'C:\work\android-sdk\android-sdk-windows\platform-tools\adb.exe -P 5037 -s 66B0220221000613 shell cmd package resolve-activity --brief ****’
�[38;5;48m[ADB]�[0m Running 'C:\work\android-sdk\android-sdk-windows\platform-tools\adb.exe -P 5037 -s 66B0220221000613 shell am start-activity -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.huawei.android.internal.app/.HwResolverActivity'
�[38;5;32m[AndroidUiautomator2Driver@2dd1 (eee974b8)]�[0m Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.huawei.android.internal.app/.HwResolverActivity }
�[38;5;32m[AndroidUiautomator2Driver@2dd1 (eee974b8)]�[0m Responding to client with driver.execute() result: null
�[38;5;0m[HTTP]�[0m �[37m<-- POST /session/eee974b8-15b0-487d-b1f5-f8ec38b69d5f/execute/sync �[39m�[32m200�[39m �[90m348 ms - 14�[39m
�[38;5;0m[HTTP]�[0m �[90m�[39m
�[38;5;0m[HTTP]�[0m �[37m-->�[39m �[37mDELETE�[39m �[37m/session/eee974b8-15b0-487d-b1f5-f8ec38b69d5f�[39m
�[38;5;0m[HTTP]�[0m �[90m{}�[39m
�[38;5;32m[AndroidUiautomator2Driver@2dd1 (eee974b8)]�[0m Calling AppiumDriver.deleteSession() with args: ["eee974b8-15b0-487d-b1f5-f8ec38b69d5f"]
�[38;5;16m[AppiumDriver@4cc4]�[0m Event 'quitSessionRequested' logged at 1749005001225 (10:43:21 GMT+0800 (China Standard Time))
�[38;5;16m[AppiumDriver@4cc4]�[0m Removing session eee974b8-15b0-487d-b1f5-f8ec38b69d5f from our master session list`

[pppppino]

by the way, I could activate the same app in other android devices(I have tried 4 android devices), only this honnor V30 have this issue

[pppppino]

by the way, I could solve this issue by using "mobile: startActivity", but I hope you could check why "mobile: activateApp" can not work, thanks

[KazuCocoa]

What activity can the device launch then?

uia2 driver tries to build the command by reading the package info as:
https://github.com/appium/appium-adb/blob/96ca96e8b09455163d9a7d84632c3ce169e78feb/lib/tools/app-commands.js#L639-L687
It generated 'C:\work\android-sdk\android-sdk-windows\platform-tools\adb.exe -P 5037 -s 66B0220221000613 shell am start-activity -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.huawei.android.internal.app/.HwResolverActivity'.

I guess the device has a special config to control activity launch. If you could find a better launching argument for the device, you'll need to build the start activity command via https://github.com/appium/appium-uiautomator2-driver?tab=readme-ov-file#mobile-startactivity. Although I feel it is more device specific config related.