MAUI App Keeps Crashing After Launching App Using Appium Return ‘com.companyname.mauiapp1.crc64e632a077a20c694c.MainActivity’ never started. error

Shooter128 · January 30, 2024, 8:51am

Hello, I am facing an issue when trying to launch app using Appium, I would be grateful if anyone would be able to help my situation.
The issue is whenever I am trying to launch my app using Appium it will launch then crash instantly. Whenever I try to open manually it continues to crash upon launching as well

// Adding Capabilities to Driver for Starting App
androidOptions.AddAdditionalCapability("appium:automationName", "UiAutomator2"); // Always should be uiautomator2
androidOptions.AddAdditionalCapability("platformName", "android"); 
androidOptions.AddAdditionalCapability("appium:udid", "a0ee97d1");
androidOptions.AddAdditionalCapability("appium:appPackage", com.companyname.mauiapp1);
androidOptions.AddAdditionalCapability("appium:appWaitActivity", "crc64794a002ba88aeb57.MainActivity");
androidOptions.AddAdditionalCapability("appium:forceAppLaunch", true);
androidOptions.AddAdditionalCapability("appium:optionalIntentArguments", "-n com.companyname.boostorder.arclight.rep/crc64794a002ba88aeb57.MainActivity");
androidOptions.AddAdditionalCapability("appium:shouldTerminateApp", true);

Tried with a new empty Maui App (.NET 8) as well, the same issue is also happening, it will launch the app briefly and closes it again

Appium Server Logs:

The error message I have from executing the test case is
‘com.companyname.mauiapp1.crc64e632a077a20c694c.MainActivity’ never started. Consider checking the driver’s troubleshooting documentation

wreed · January 30, 2024, 4:47pm

Are you asking how to get the correct package and activity?

https://www.automationtestinghub.com/apppackage-and-appactivity-name/

Shooter128 · January 31, 2024, 2:05am

Hi Wreed, nope I have already gotten the app package and activity through adb

The issue I am facing is after launching the app using appium, the app crashes instantly and will continue to do so, I would like to see if anyone has any idea about this situation and gladly accept any help. It has been bugging me for days

wreed · January 31, 2024, 3:35am

Can you post a full log?

Shooter128 · January 31, 2024, 6:33am

Hello Wreed, this is the full log

 --> POST /session

[HTTP] {“desiredCapabilities”:{“appium:automationName”:“UiAutomator2”,“platformName”:“Android”,“appium:udid”:“a0ee97d1”,“appium:appPackage”:“com.companyname.mauiapp1”,“appium:appWaitActivity”:“com.companyname.mauiapp1.MainActivity”},“capabilities”:{“firstMatch”:[{“appium:automationName”:“UiAutomator2”,“platformName”:“Android”,“appium:udid”:“a0ee97d1”,“appium:appPackage”:“com.companyname.mauiapp1”,“appium:appWaitActivity”:“com.companyname.mauiapp1.MainActivity”}]}}
[AppiumDriver@8f76] Calling AppiumDriver.createSession() with args: [{“appium:automationName”:“UiAutomator2”,“platformName”:“Android”,“appium:udid”:“a0ee97d1”,“appium:appPackage”:“com.companyname.mauiapp1”,“appium:appWaitActivity”:“com.companyname.mauiapp1.MainActivity”},null,{“firstMatch”:[{“appium:automationName”:“UiAutomator2”,“platformName”:“Android”,“appium:udid”:“a0ee97d1”,“appium:appPackage”:“com.companyname.mauiapp1”,“appium:appWaitActivity”:“com.companyname.mauiapp1.MainActivity”}]}]
[AppiumDriver@8f76] Event ‘newSessionRequested’ logged at 1706671770565 (11:29:30 GMT+0800 (Singapore Standard Time))
[Appium] Attempting to find matching driver for automationName ‘UiAutomator2’ and platformName ‘Android’
[Appium] The ‘uiautomator2’ driver was installed and matched caps.
[Appium] Will require it at C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver
[Appium] Requiring driver at C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\build\index.js
[AppiumDriver@8f76] Appium v2.4.1 creating new AndroidUiautomator2Driver (v2.37.0) session
[AppiumDriver@8f76] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
[AppiumDriver@8f76] Appium’s BaseDriver version is 9.5.0
[AppiumDriver@8f76] AndroidUiautomator2Driver’s BaseDriver version is 9.5.0
[AndroidUiautomator2Driver@ad6f] Creating session with W3C capabilities: {
[AndroidUiautomator2Driver@ad6f] “alwaysMatch”: {
[AndroidUiautomator2Driver@ad6f] “platformName”: “Android”,
[AndroidUiautomator2Driver@ad6f] “appium:automationName”: “UiAutomator2”,
[AndroidUiautomator2Driver@ad6f] “appium:udid”: “a0ee97d1”,
[AndroidUiautomator2Driver@ad6f] “appium:appPackage”: “com.companyname.mauiapp1”,
[AndroidUiautomator2Driver@ad6f] “appium:appWaitActivity”: “com.companyname.mauiapp1.MainActivity”
[AndroidUiautomator2Driver@ad6f] },
[AndroidUiautomator2Driver@ad6f] “firstMatch”: [
[AndroidUiautomator2Driver@ad6f] {}
[AndroidUiautomator2Driver@ad6f] ]
[AndroidUiautomator2Driver@ad6f] }
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Session created with session id: 0b58a9d4-c257-42d4-99c1-c96e593cb634
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Starting ‘com.companyname.mauiapp1’ directly on the device
[ADB] Using ‘adb.exe’ from ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 start-server’
[AndroidDriver] Retrieving device list
[ADB] Trying to find connected Android devices
[ADB] Getting connected devices
[ADB] Connected devices: [{“udid”:“a0ee97d1”,“state”:“device”}]
[AndroidDriver] Using device: a0ee97d1
[ADB] Using ‘adb.exe’ from ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 start-server’
[ADB] Setting device id to a0ee97d1
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell getprop ro.build.version.sdk’
[ADB] Current device property ‘ro.build.version.sdk’: 25
[ADB] Device API level: 25
[AndroidDriver] No app sent in, not parsing package/activity
[AndroidDriver] Pushing settings apk to device…
[ADB] Getting package info for ‘io.appium.settings’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys package io.appium.settings’
[ADB] The version name of the installed ‘io.appium.settings’ is greater or equal to the application version name (‘5.2.0’ >= ‘5.2.0’)
[ADB] There is no need to install/upgrade ‘C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\node_modules\io.appium.settings\apks\settings_apk-debug.apk’
[ADB] Getting IDs of all ‘io.appium.settings’ processes
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell ‘pgrep --help; echo $?’’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell ‘pgrep ^appium\.settings$ || pgrep ^io\.appium\.setti$’’
[ADB] Getting IDs of all ‘io.appium.settings’ processes
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell ‘pgrep ^appium\.settings$ || pgrep ^io\.appium\.setti$’’
[ADB] Starting Appium Settings app
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell am start -n io.appium.settings/.Settings -a android.intent.action.MAIN -c android.intent.category.LAUNCHER’
[ADB] Getting IDs of all ‘io.appium.settings’ processes
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell ‘pgrep ^appium\.settings$ || pgrep ^io\.appium\.setti$’’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell appops set io.appium.settings android:mock_location allow’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell “[ -e ‘/data/local/tmp/mock_apps.json’ ] && echo PASS”’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell cat /data/local/tmp/mock_apps.json’
[Logcat] Starting logs capture with command: ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe’ -P 5037 -s a0ee97d1 logcat -v threadtime
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Forwarding UiAutomator2 Server port 6790 to local port 8200
[ADB] Forwarding system: 8200 to device: 6790
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 forward tcp:8200 tcp:6790’
[ADB] Checking app cert for C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v5.15.0.apk
[ADB] Checking app cert for C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk
[ADB] Using the previously cached signature entry for ‘appium-uiautomator2-server-debug-androidTest.apk’
[ADB] sha256 hash did match for ‘appium-uiautomator2-server-debug-androidTest.apk’
[ADB] Getting install status for io.appium.uiautomator2.server.test
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell pm path io.appium.uiautomator2.server.test’
[ADB] Using the previously cached signature entry for ‘appium-uiautomator2-server-v5.15.0.apk’
[ADB] sha256 hash did match for ‘appium-uiautomator2-server-v5.15.0.apk’
[ADB] Getting package info for ‘io.appium.uiautomator2.server’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys package io.appium.uiautomator2.server’
[ADB] ‘io.appium.uiautomator2.server.test’ is installed
[ADB] The version name of the installed ‘io.appium.uiautomator2.server’ is greater or equal to the application version name (‘5.15.0’ >= ‘5.15.0’)
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Server packages status: [{“wasSigned”:true,“installState”:“sameVersionInstalled”,“appPath”:“C:\Users\Demo\.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v5.15.0.apk”,“appId”:“io.appium.uiautomator2.server”},{“wasSigned”:true,“installState”:“sameVersionInstalled”,“appPath”:“C:\Users\Demo\.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk”,“appId”:“io.appium.uiautomator2.server.test”}]
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Server packages are not going to be (re)installed
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Waiting up to 30000ms for services to be available
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell pm list instrumentation’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Instrumentation target ‘io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner’ is available
[ADB] Adding packages [“io.appium.settings”,“io.appium.uiautomator2.server”,“io.appium.uiautomator2.server.test”] to Doze whitelist
[ADB] Got the following command chunks to execute: [[“dumpsys”,“deviceidle”,“whitelist”,"+io.appium.settings",";",“dumpsys”,“deviceidle”,“whitelist”,"+io.appium.uiautomator2.server",";",“dumpsys”,“deviceidle”,“whitelist”,"+io.appium.uiautomator2.server.test",";"]]
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys deviceidle whitelist +io.appium.settings ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server.test ;’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] No app capability. Assuming it is already on the device
[ADB] Getting install status for com.companyname.mauiapp1
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell pm path com.companyname.mauiapp1’
[ADB] ‘com.companyname.mauiapp1’ is installed
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell am force-stop com.companyname.mauiapp1’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell pm clear com.companyname.mauiapp1’
[AndroidDriver] Performed fast reset on the installed ‘com.companyname.mauiapp1’ application (stop and clear)
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Performing shallow cleanup of automation leftovers
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] No obsolete sessions have been detected (socket hang up)
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell am force-stop io.appium.uiautomator2.server.test’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Starting UIAutomator2 server 5.15.0
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Using UIAutomator2 server from ‘C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v5.15.0.apk’ and test from ‘C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Waiting up to 30000ms for UiAutomator2 to be online…
[ADB] Creating ADB subprocess with args: ["-P",“5037”,"-s",“a0ee97d1”,“shell”,“am”,“instrument”,"-w","-e",“disableAnalytics”,“true”,“io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner”]
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Matched ‘/status’ to command name ‘getStatus’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] socket hang up
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Matched ‘/status’ to command name ‘getStatus’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] socket hang up
[Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Matched ‘/status’ to command name ‘getStatus’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] socket hang up
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Matched ‘/status’ to command name ‘getStatus’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Got response with status 200: {“sessionId”:“None”,“value”:{“message”:“UiAutomator2 Server is ready to accept commands”,“ready”:true}}
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] The initialization of the instrumentation process took 3168ms
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Matched ‘/session’ to command name ‘createSession’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [POST /session] to [POST http://127.0.0.1:8200/session] with body: {“capabilities”:{“firstMatch”:[{“platformName”:“Android”,“automationName”:“UiAutomator2”,“udid”:“a0ee97d1”,“appPackage”:“com.companyname.mauiapp1”,“appWaitActivity”:“com.companyname.mauiapp1.MainActivity”,“platform”:“LINUX”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“networkConnectionEnabled”:true,“locationContextEnabled”:false,“warnings”:{},“desired”:{“platformName”:“Android”,“automationName”:“UiAutomator2”,“udid”:“a0ee97d1”,“appPackage”:“com.companyname.mauiapp1”,“appWaitActivity”:“com.companyname.mauiapp1.MainActivity”},“deviceName”:“a0ee97d1”,“deviceUDID”:“a0ee97d1”}],“alwaysMatch”:{}}}
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Got response with status 200: {“sessionId”:“a70f4988-3d2f-4bdf-adae-8c978d78d431”,“value”:{“capabilities”:{“firstMatch”:[{“platformName”:“Android”,“automationName”:“UiAutomator2”,“udid”:“a0ee97d1”,“appPackage”:“com.companyname.mauiapp1”,“appWaitActivity”:“com.companyname.mauiapp1.MainActivity”,“platform”:“LINUX”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“networkConnectionEnabled”:true,“locationContextEnabled”:false,“warnings”:{},“desired”:{“platformName”:“Android”,“automationName”:“UiAutomator2”,“udid”:“a0ee97d1”,“appPackage”:“com.companyname.mauiapp1”,“appWaitActivity”:“com.companyname.mauiapp1.MainActivity”},“deviceName”:“a0ee97d1”,“deviceUDID”:“a0ee97d1”}],“alwaysMatch”:{}},“sessionId”:“a70f4988-3d2f-4bdf-adae-8c978d78d431”}}
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Determined the downstream protocol as ‘W3C’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [GET /appium/device/pixel_ratio] to [GET http://127.0.0.1:8200/session/a70f4988-3d2f-4bdf-adae-8c978d78d431/appium/device/pixel_ratio] with no body
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Matched ‘/appium/device/system_bars’ to command name ‘getSystemBars’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [GET /appium/device/system_bars] to [GET http://127.0.0.1:8200/session/a70f4988-3d2f-4bdf-adae-8c978d78d431/appium/device/system_bars] with no body
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Matched ‘/window/current/size’ to command name ‘getWindowSize’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [GET /window/current/size] to [GET http://127.0.0.1:8200/session/a70f4988-3d2f-4bdf-adae-8c978d78d431/window/current/size] with no body
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [GET /appium/device/info] to [GET http://127.0.0.1:8200/session/a70f4988-3d2f-4bdf-adae-8c978d78d431/appium/device/info] with no body
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Got response with status 200: {“sessionId”:“a70f4988-3d2f-4bdf-adae-8c978d78d431”,“value”:2}
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Got response with status 200: {“sessionId”:“a70f4988-3d2f-4bdf-adae-8c978d78d431”,“value”:{“statusBar”:48}}
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Got response with status 200: {“sessionId”:“a70f4988-3d2f-4bdf-adae-8c978d78d431”,“value”:{“height”:1280,“width”:720}}
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Got response with status 200: {“sessionId”:“a70f4988-3d2f-4bdf-adae-8c978d78d431”,“value”:{“androidId”:“410fd6bc8fbbd1ce”,“apiVersion”:“25”,“bluetooth”:{“state”:“ON”},“brand”:“Android”,“carrierName”:"",“displayDensity”:320,“locale”:“en_US”,“manufacturer”:“UBX”,“model”:“i6310T”,“networks”:[{“capabilities”:{“SSID”:null,“linkDownBandwidthKbps”:1048576,“linkUpstreamBandwidthKbps”:1048576,“networkCapabilities”:“NET_CAPABILITY_NOT_METERED,NET_CAPABILITY_NOT_RESTRICTED,NET_CAPABILITY_NOT_VPN,NET_CAPABILITY_NOT_ROAMING,NET_CAPABILITY_INTERNET,NET_CAPABILITY_TRUSTED,NET_CAPABILITY_VALIDATED”,“signalStrength”:-52,“transportTypes”:“TRANSPORT_WIFI”},“detailedState”:“CONNECTED”,“extraInfo”:"“Instanture”",“isAvailable”:true,“isConnected”:true,“isFailover”:false,“isRoaming”:false,“state”:“CONNECTED”,“subtype”:0,“subtypeName”:"",“type”:1,“typeName”:“WIFI”}],“platformVersion”:“7.1.1”,“realDisplaySize”:“720x1280”,“timeZone”:“Asia/Kuala_Lumpur”}}
[AndroidDriver] Screen already unlocked, doing nothing
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Starting 'com.companyname.mauiapp1/undefined and waiting for ‘com.companyname.mauiapp1/com.companyname.mauiapp1.MainActivity’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell am start -W -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000’
[ADB] Waiting up to 20000ms for activity matching pkg: ‘com.companyname.mauiapp1’ and activity: ‘com.companyname.mauiapp1.MainActivity’ to be focused
[ADB] Possible activities, to be checked: ‘com.companyname.mauiapp1.MainActivity’, ‘com.companyname.mauiapp1.com.companyname.mauiapp1.MainActivity’
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.companyname.mauiapp1’ and fully qualified activity name : ‘crc64e632a077a20c694c.MainActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.companyname.mauiapp1’ and fully qualified activity name : ‘crc64e632a077a20c694c.MainActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.companyname.mauiapp1’ and fully qualified activity name : ‘crc64e632a077a20c694c.MainActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.companyname.mauiapp1’ and fully qualified activity name : ‘crc64e632a077a20c694c.MainActivity’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[ADB] Getting focused package and activity
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell dumpsys window windows’
[ADB] Found package: ‘com.android.launcher3’ and fully qualified activity name : ‘com.android.launcher3.Launcher’
[ADB] Incorrect package and activity. Retrying.
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Deleting UiAutomator2 session
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Deleting UiAutomator2 server session
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Matched ‘/’ to command name ‘deleteSession’
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Proxying [DELETE /] to [DELETE http://127.0.0.1:8200/session/a70f4988-3d2f-4bdf-adae-8c978d78d431] with no body
[AndroidUiautomator2Driver@ad6f (0b58a9d4)] Got response with status 200: {“sessionId”:“a70f4988-3d2f-4bdf-adae-8c978d78d431”,“value”:null}
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 shell am force-stop com.companyname.mauiapp1’
[Instrumentation] .
[Instrumentation] Time: 24.042
[Instrumentation]
[Instrumentation] OK (1 test)
[Instrumentation] The process has exited with code 0
[Logcat] Stopping logcat capture
[ADB] Removing forwarded port socket connection: 8200
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s a0ee97d1 forward --remove tcp:8200’
[AppiumDriver@8f76] Event ‘newSessionStarted’ logged at 1706671806190 (11:30:06 GMT+0800 (Singapore Standard Time))
[AppiumDriver@8f76] Encountered internal error running command: Error: Cannot start the ‘com.companyname.mauiapp1’ application. Consider checking the driver’s troubleshooting documentation. Original error: ‘com.companyname.mauiapp1.MainActivity’ or ‘com.companyname.mauiapp1.com.companyname.mauiapp1.MainActivity’ never started. Consider checking the driver’s troubleshooting documentation.
[AppiumDriver@8f76] at ADB.startApp (C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-adb\lib\tools\apk-utils.js:189:11)
[AppiumDriver@8f76] at AndroidUiautomator2Driver.ensureAppStarts (C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\lib\driver.ts:702:5)
[AppiumDriver@8f76] at AndroidUiautomator2Driver.startUiAutomator2Session (C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\lib\driver.ts:555:7)
[AppiumDriver@8f76] at AndroidUiautomator2Driver.createSession (C:\Users\Demo.appium\node_modules\appium-uiautomator2-driver\lib\driver.ts:298:22)
[AppiumDriver@8f76] at AppiumDriver.createSession (C:\Users\Demo\AppData\Roaming\npm\node_modules\appium\lib\appium.js:717:35)
[HTTP] <-- POST /session 500 35631 ms - 1202
[HTTP]

wreed · January 31, 2024, 4:39pm

Troubleshooting for Uiautomator2:

Shooter128 · February 1, 2024, 7:51am

Hi Wreed, I have looked at the guide, but it is still not solving my issue

Shooter128 · February 1, 2024, 8:18am

wreed · February 1, 2024, 5:06pm

Ah, so it’s a bug in the app. Need to talk to developers for that.

Shooter128 · February 2, 2024, 9:39am

I tried to launch using Appium on a completely new MAUI project, it is showing this error message after I try to run my test as well. So I am wondering is it my code issue or something with Appium on MAUI

wreed · February 2, 2024, 5:51pm

Android OS is reporting a bug in the app. I’m sorry I don’t know anything about coding MAUI apps.

Seems like there is a lot of discussion about MAUI apps. You might want to check out these resources:

mau app discussion forum?

Shooter128 · February 6, 2024, 3:22am

Thank you Wreed, you have been a great help. Unfortunately it doesn’t have the post related to my issue

wreed · February 6, 2024, 5:04am

One last try. I found a tutorial from Microsoft that gives code for a sample MAUI app and goes into detail about testing it with Appium. I’m out of my depth here but maybe it will help:

PramodKarande · February 14, 2024, 6:43am

@Shooter128, me too facing same issue with Maui apps
if you find any solution, plz write it here

Shooter128 · February 16, 2024, 1:53am

Hi @PramodKarande, I fixed it by deploying release mode of the app instead of debug mode