appium: Error on default activity that starts chrome browser on android 13

[update] https://github.com/appium/appium/issues/17492#issuecomment-1314708723 is a workaround in Appium

The problem

When starting chrome browser on android 13 I get Activity class {com.android.chrome/com.google.android.apps.chrome.Main} does not exist. It comes with the fact that chrome browser is started diiferently on newest android version (full description here (https://automationchronicles.com/error-when-opening-chrome-on-android-13-via-adb/). My solution is changing activity to com.google.android.apps.chrome.IntentDispatcher with added -d flag and default url or changing action to android.intent.action.MAIN.

Environment

  • Appium version: 1.22.3
  • Desktop OS/version used to run Appium: Macos 12.5.1
  • Mobile platform/version under test: Android 13

Link to Appium logs

https://gist.github.com/Hubert-Rudzik/3daaac080a6b6b42347569f0dde4afcd

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (4 by maintainers)

Most upvoted comments

According to https://bugs.chromium.org/p/chromedriver/issues/detail?id=4193&sort=status -id&q=com.android.chrome&can=2, Chrome 110 will have a fix for this issue. Maybe we no longer need this workaround after the version.