Appium problems encountered in the use of

1, org.openqa.selenium.sessionnotcreatedexception:a new session could not be created. (Original error:the following desired capabilities is required, but were not provided:devicename)

Workaround: The device name is not added

Capabilities.setcapability ("DeviceName", "Emulator");

2, run Appium, run error, prompt detection device, run cmd, input ADB devices hint error, no display device UID, Internet search said installed 360 mobile phone assistant caused the conflict, 360 mobile phone assistant deleted, sure enough.

3. Get the App startup activity

1) point the current path to the Build-tools directory of the SDK and put the APK file in: Execute the following command:. \AAPT dump badging xxx.apk command gets the in-package information. Note that the startup class name cannot be wrong with a letter, note the Launchable-activity property

2) No apk, the app is already installed on the phone or virtual machine. You can use the Logcat command

. Clear Logcat content, use command adb logcat-c

. Start Logcat, use the command adb logcat activitymanager:i *:s

4, use Appiumdriver error: jar with java-client-2.2.0, should use Androiddriver or 1.3.4 java-client

Also encountered a variety of problems, some have not resolved, not yet to be continued

Appium problems encountered in the use of