# AndroidUiautomator2Driver not created at first test in M1 Chip **URL:** \ **Category:** Support\ **Created:** [July 24, 2022, 11:51pm UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885 "2022-07-24T23:51:59Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![IMOBILETester](https://discuss.appium.io/user_avatar/discuss.appium.io/imobiletester/32/8835_2.png) [@IMOBILETester](https://discuss.appium.io/u/IMOBILETester)\ **Post date:** [July 24, 2022, 11:51pm UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/1 "2022-07-24T23:51:59Z")
Hi all, I’m using M1 chip : MacPro with below details for my appium automation.Before I used Intel, same framework is used to fine, now I’m using M1 chip. I have other configuration for M1 in bash profile. While running, I noticed My UIAutomator2 server is not running in my first test, it started working after 3rd test. My emulator is not loading quite well at first test, then automatically it starts working fine after few test. I din’t understand it’s my driver issue or emulator issue Intelli J : IntelliJ IDEA 2022.1.3 serenity.version:2.3.12 java-client : 8.0.0 selenium-java:3.141.59 UIAutomator2 server 4.27.0 Scenario: Valid customer login to the App from Account page # src/test/resources/features/Account/AccountSignIn.feature:8 2022-07-25 11:17:52 INFO SerenityReporter:194 - Running feature from 2022-07-25 11:17:52 INFO :148 - * * * |\_ _| **/ \_\_|| / \_\_||/ \ | \_ \_ | | \_ \ | | | | \_ \ | | \_ \ | | / \_ \ | |) || | | | | | | | | | | | \_\_\_) || | \_\_\_) || |/ \_\_\_ | \_ \< | | | |**| || | || |\_\_\_\_\_|_ **_/ |_| |** _/ |/_/ \_\_| \_|_| |\_\_\_\_\_|_\_\_\_/ * * * [Appium] Welcome to Appium v1.22.3 [Appium] Non-default server args: [Appium] address: 127.0.0.1 [Appium] loglevel: info [Appium] avd: Pixel\_2\_API\_30 [Appium] Deprecated server args: [Appium] --avd =\> --default-capabilities [Appium] Default capabilities, which will be added to each request unless overridden by desired capabilities: [Appium] avd: Pixel\_2\_API\_30 [Appium] Appium REST http interface listener started on 127.0.0.1:4723 [HTTP] --\> POST /wd/hub/session ---
**Author:** ![wreed](https://discuss.appium.io/letter_avatar_proxy/v4/letter/w/919ad9/32.png) [@wreed](https://discuss.appium.io/u/wreed)\ **Post date:** [July 25, 2022, 4:17am UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/3 "2022-07-25T04:17:25Z")
> [@IMOBILETester](#): > > [BaseDriver] Number capability passed in as string. Functionality may be compromised. > [Appium] Appium v1.22.3 creating new AndroidUiautomator2Driver (v1.70.1) session > [BaseDriver] Number capability passed in as string. Functionality may be compromised. > [BaseDriver] Capability ‘fullReset’ changed from string to boolean. This may cause unexpected behavior > [BaseDriver] Capability ‘allowTestPackages’ changed from string to boolean. This may cause unexpected behavior > [@IMOBILETester](#): > > [ADB] Found 2 ‘build-tools’ folders under ‘/Users/390099/Library/Android/Sdk’ (newest first): > [ADB] /Users/390099/Library/Android/Sdk/build-tools/33.0.0 > [ADB] /Users/390099/Library/Android/Sdk/build-tools/30.0.3 > [ADB] Using ‘adb’ from ‘/Users/390099/Library/Android/Sdk/platform-tools/adb’ > [ADB] Using ‘emulator’ from ‘/Users/390099/Library/Android/Sdk/emulator/emulator’ > [ADB] [AVD OUTPUT] WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator. > [ADB] [AVD OUTPUT] WARNING | cannot add library /Users/390099/Library/Android/sdk/emulator/qemu/darwin-aarch64/lib64/vulkan/libvulkan.dylib: failed > [ADB] [AVD OUTPUT] INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on\_new\_posture\_requested(int) ((null):0, (null)) > [ADB] [AVD OUTPUT] INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on\_dismiss\_posture\_selection\_dialog() ((null):0, (null)) > [ADB] [AVD OUTPUT] INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on\_new\_resizable\_requested(PresetEmulatorSizeType) ((null):0, (null)) > [ADB] [AVD OUTPUT] INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on\_dismiss\_resizable\_dialog() ((null):0, (null)) You have all these _warnings_ in your log and an indication that not fixing these may affect performance. Can I ask why you choose not to fix these? This really seems like a setup issue. For capabilities you can reference this link for what values should be supplied. Note that there is a big difference between 1000 and ‘1000’, and, false and ‘false’: [https://appium.io/docs/en/writing-running-appium/caps/](https://appium.io/docs/en/writing-running-appium/caps/) M1 chip seems like a red herring. ---
**Author:** ![IMOBILETester](https://discuss.appium.io/user_avatar/discuss.appium.io/imobiletester/32/8835_2.png) [@IMOBILETester](https://discuss.appium.io/u/IMOBILETester)\ **Post date:** [July 25, 2022, 4:25am UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/4 "2022-07-25T04:25:25Z")
Hi Wreed. Thanks for looking, yeah i fixed those warnings. But still notice my emulator loads slowly ,sometimes cold boot resolves the issue.but not every time. [Appium] Welcome to Appium v1.22.3 [Appium] Non-default server args: [Appium] address: 127.0.0.1 [Appium] loglevel: info [Appium] avd: Pixel\_2\_API\_30 [Appium] Deprecated server args: [Appium] --avd =\> --default-capabilities [Appium] Default capabilities, which will be added to each request unless overridden by desired capabilities: [Appium] avd: Pixel\_2\_API\_30 [Appium] Appium REST http interface listener started on 127.0.0.1:4723 * * * [BaseDriver] The following capabilities are not standard capabilities and should have an extension prefix: [BaseDriver] host [BaseDriver] js [BaseDriver] loggingPrefs [BaseDriver] port [BaseDriver] avd [BaseDriver] Number capability passed in as string. Functionality may be compromised. [Appium] Appium v1.22.3 creating new AndroidUiautomator2Driver (v1.70.1) session [BaseDriver] Number capability passed in as string. Functionality may be compromised. [BaseDriver] Capability ‘fullReset’ changed from string to boolean. This may cause unexpected behavior [BaseDriver] Capability ‘allowTestPackages’ changed from string to boolean. This may cause unexpected behavior [BaseDriver] Capability ‘newCommandTimeout’ changed from string (‘1000’) to integer (1000). This may cause unexpected behavior [BaseDriver] The following capabilities were provided, but are not recognized by Appium: [BaseDriver] host [BaseDriver] js [BaseDriver] loggingPrefs [BaseDriver] port [BaseDriver] autoAcceptAlerts [BaseDriver] autoDismissAlerts [BaseDriver] Session created with session id: 750fc18b-79d1-463f-9803-a152b198ff03 net.thucydides.core.webdriver.DriverConfigurationError: Could not instantiate class io.appium.java\_client.AppiumDriver Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’ System info: host: ‘ITM306880’, ip: ‘2406:e003:1055:b101:c1d2:372d:8c39:6860%en0’, os.name: ‘Mac OS X’, os.arch: ‘x86\_64’, os.version: ‘10.16’, java.version: ‘1.8.0\_242-release’ Driver info: driver.version: AndroidDriver remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘/Users/390099/Library/Android/Sdk/platform-tools/adb -P 5037 -s emulator-5554 shell ‘settings delete global hidden\_api\_policy\_pre\_p\_apps;settings delete global hidden\_api\_policy\_p\_apps;settings delete global hidden\_api\_policy’’ exited with code 20’; Command output: cmd: Can’t find service: settings cmd: Can’t find service: settings cmd: Can’t find service: settings ---
**Author:** ![wreed](https://discuss.appium.io/letter_avatar_proxy/v4/letter/w/919ad9/32.png) [@wreed](https://discuss.appium.io/u/wreed)\ **Post date:** [July 25, 2022, 4:23pm UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/5 "2022-07-25T16:23:32Z")
> [@IMOBILETester](#): > > yeah i fixed those warnings Did you post the wrong log? Still seeing same errors. > [@IMOBILETester](#): > > [BaseDriver] Number capability passed in as string. Functionality may be compromised. > [Appium] Appium v1.22.3 creating new AndroidUiautomator2Driver (v1.70.1) session > [BaseDriver] Number capability passed in as string. Functionality may be compromised. > [BaseDriver] Capability ‘fullReset’ changed from string to boolean. This may cause unexpected behavior > [BaseDriver] Capability ‘allowTestPackages’ changed from string to boolean. This may cause unexpected behavior > [BaseDriver] Capability ‘newCommandTimeout’ changed from string (‘1000’) to integer (1000). This may cause unexpected behavior > [@IMOBILETester](#): > > [BaseDriver] The current application path ‘.//src/test/resources/APK/NoelLeeming-qat-release.apk’ is not absolute and has been rewritten to ‘/Users/390099/Documents/repo/mob-qa-nlapp-android/src/test/resources/APK/NoelLeeming-qat-release.apk’. Consider using absolute paths rather than relative > [@IMOBILETester](#): > > [ADB] Found 1 ‘build-tools’ folders under ‘/Users/390099/Library/Android/Sdk’ (newest first): > [ADB] /Users/390099/Library/Android/Sdk/build-tools/33.0.0 > [ADB] Using ‘adb’ from ‘/Users/390099/Library/Android/Sdk/platform-tools/adb’ > [ADB] Using ‘emulator’ from ‘/Users/390099/Library/Android/Sdk/emulator/emulator’ > [ADB] [AVD OUTPUT] WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator. > [ADB] [AVD OUTPUT] WARNING | cannot add library /Users/390099/Library/Android/sdk/emulator/qemu/darwin-aarch64/lib64/vulkan/libvulkan.dylib: failed > [ADB] [AVD OUTPUT] INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on\_new\_posture\_requested(int) ((null):0, (null)) > [ADB] [AVD OUTPUT] INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on\_dismiss\_posture\_selection\_dialog() ((null):0, (null)) > [ADB] [AVD OUTPUT] INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on\_new\_resizable\_requested(PresetEmulatorSizeType) ((null):0, (null)) > [ADB] [AVD OUTPUT] INFO | Warning: QMetaObject::connectSlotsByName: No matching signal for on\_dismiss\_resizable\_dialog() ((null):0, (null)) It looks like you have errors in both Appium and the underlying ADB. I think you can fix Appium errors by fixing the capabilities as noted above. Maybe try clean install for ADB? ---
**Author:** ![wreed](https://discuss.appium.io/letter_avatar_proxy/v4/letter/w/919ad9/32.png) [@wreed](https://discuss.appium.io/u/wreed)\ **Post date:** [July 25, 2022, 4:26pm UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/6 "2022-07-25T16:26:02Z")
> [@IMOBILETester](#): > > [ADB] [AVD OUTPUT] WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator. > ---
**Author:** ![IMOBILETester](https://discuss.appium.io/user_avatar/discuss.appium.io/imobiletester/32/8835_2.png) [@IMOBILETester](https://discuss.appium.io/u/IMOBILETester)\ **Post date:** [July 26, 2022, 5:04am UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/7 "2022-07-26T05:04:10Z")
Thanks Wreed for guidance. All above issues are resolved. M1 chip having compatible issue with old android studio. I downloaded latest one, then above issue is resolved. I have set capability in class than property file. ---
**Author:** ![wreed](https://discuss.appium.io/letter_avatar_proxy/v4/letter/w/919ad9/32.png) [@wreed](https://discuss.appium.io/u/wreed)\ **Post date:** [July 26, 2022, 4:16pm UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/8 "2022-07-26T16:16:10Z")
I’m glad this worked for you. Good luck! ---
**Author:** ![ido\_oserovitz](https://discuss.appium.io/user_avatar/discuss.appium.io/ido_oserovitz/32/9832_2.png) [@ido\_oserovitz](https://discuss.appium.io/u/ido_oserovitz)\ **Post date:** [July 27, 2022, 3:38pm UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/9 "2022-07-27T15:38:28Z")
Although you solved it. Please note: 1. when you create an avd (emulator) with android studios’s UI, make sure you choose an ARM Image (ABI: arm64-v8a) which is compatible for a M1 device and that’s why your emulator might not function well as you mentioned. 2. I updated my repo to use java-client 8.0.0 and it has an issue with the plafotmName capability which was fixed in version 8.1.1 ([java-client release notes](https://github.com/appium/java-client/releases#:~:text=Perform%20safe%20typecast%20while%20getting%20the%20platform%20name.%20%231702) ) so I had to update. If I remember correctly, it caused different errors regarding the “ **settings delete global hidden\_api\_policy\_p\_apps** ” so it maybe worth to update your client as well if it will happen again. ---
**Author:** ![IMOBILETester](https://discuss.appium.io/user_avatar/discuss.appium.io/imobiletester/32/8835_2.png) [@IMOBILETester](https://discuss.appium.io/u/IMOBILETester)\ **Post date:** [July 27, 2022, 10:39pm UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/10 "2022-07-27T22:39:28Z")
Thanks for suggestion.I’m getting error ( Dependency Not found) ,if i change Java client as 8.1.1. What’s your maven version?Mine as follows. \2.3.12\ \2.3.12\ \2.3.12\ \6.9.1\ ---
**Author:** ![ido\_oserovitz](https://discuss.appium.io/user_avatar/discuss.appium.io/ido_oserovitz/32/9832_2.png) [@ido\_oserovitz](https://discuss.appium.io/u/ido_oserovitz)\ **Post date:** [July 28, 2022, 6:31am UTC](https://discuss.appium.io/t/androiduiautomator2driver-not-created-at-first-test-in-m1-chip/36885/11 "2022-07-28T06:31:38Z")
mine is: **3.8.1** after you changed the dependency you need to refresh/sync it with maven. run in terminal **mvn clean test-compile** copy from here: [https://mvnrepository.com/artifact/io.appium/java-client/8.1.1](https://mvnrepository.com/artifact/io.appium/java-client/8.1.1)