Samsung phones issue to open the app

[MarlonCCode]

Mobilewright version

0.032

Operating system

Windows 11 Pro

Target platform

Android

Device or simulator

Samsung A55 5g

Minimal reproduction

.

Actual behavior

The app basically doesn't open, when opened it loses the context of the app

Expected behavior

To be able to open it and continue with the steps

Additional context

mobilecli gets the foreground app by parsing mCurrentFocus from adb shell dumpsys window windows. Samsung One UI (Galaxy A55) doesn't output that field in dumpsys window windows — it only appears in dumpsys window (no arg). So every launchApp and getForegroundApp call hangs or fails on this

[MarlonCCode]

This is extra information from Claude:

File a bug with MobileWright at https://github.com/mobile-next/mobilewright/issues with the finding: dumpsys window windows missing mCurrentFocus on Samsung One UI / Galaxy A55. The fix in mobilecli would be to fall back to dumpsys window when the field isn't found.

[gmegidish]

@MarlonCCode I will launch a Galaxy A55 session and debug this. This is a serious bug. I will also add a regression test that we run this on a real device in the cloud so this never comes back. I'll update you shortly.

[sudarshanQeagle]

Hi @MarlonCCode could you pls refer the issue #92

[gmegidish]

@sudarshanQeagle @MarlonCCode this has been workaround by @farhanlabib in #102

I am waiting for a small fix on their side and then it will be made into a new version. Right now you can workaround with
await device.launchApp('com.example.app', { noWaitAfter: true }); // skip foreground wait

I'll update on this ticket shortly.

[gmegidish]

@MarlonCCode please seehttps://github.com//issues/92#issuecomment-4396318603
v0.0.33 solves this problem.
thank you!

[gmegidish]

Alright. Verified, closing ticket. If there is any other issue, please open a new one.