This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
21 / 27
May 2018

Appium 1.8.0 introduces full support for the W3C WebDriver specification64
(digested version of the spec39).

General

  • Minimum NodeJS21 version moved to 6
  • Add methods for
    • getting and setting the clipboard contents
    • get full screen screenshots
    • Application management
  • More efficient app downloading by caching URLs
  • All moveTo operations in touch actions now take coordinates as absolute
  • Support for registering selenium grid through HTTPS by setting the configuration
    key "hubProtocol" to "https"
  • Add otherApps desired capability, to specify array of ancillary apps to install
    on session creation

iOS

  • Support for iOS 11.3/Xcode 9.3
  • Fix handling of process arguments
  • Add capabilities
    • shutdownOtherSimulators - shutdown other running simulators at session start up
  • Add ability to record screen
  • Add support for complex gestures
  • Fix handling of custom SSL certificate on simulators
  • Better handling of xcodebuild processes
  • Maintain keychains while upgrading apps
  • Better handle simulators in unexpected states
  • Add performance measuring (see documentation58)

Android

  • Support for Android P (API Level 28)
  • Fix handling of webview contexts when resetting apps
  • Fix handling of screen recording
  • Make sure intent is broadcast when file is uploaded
  • Add possibility to broadcast device logs through WebSocket
  • Chromedriver
    • Bundle version 2.37
    • Automatically choose compatible Chromedriver for Chrome version
      • chromedriverExecutableDir capability to specify where Chromedrivers are located
      • chromedriverChromeMappingFile capability to specify what Chromedriver version corresponds to what Chrome version
  • Fix Handling of idle state waiting
  • Speed up screenshot logic in UiAutomator2
  • Allow disabling of notification watching through settings
  • Fix parsing and granting of permissions for app under test
  • Support deep linking and Android Instant Apps
  • created

    Apr '18
  • last reply

    Aug '18
  • 26

    replies

  • 6.3k

    views

  • 15

    users

  • 11

    likes

  • 13

    links

pinned globally Apr 23, '18

I am unable to apply with this build. You can find the logs below.

Guys, any introduction about this setting?

Hey :slight_smile:
can you publish the appium REST server endpoints?
thanks!

is there any documentation regarding screen recording?

For Java-Client you can check:


Hello,

When we can expect appium 1.8 dmg for mac, I am facing a problem, my all iPhone devices updated to 11.3 and now i unable to run appium on it i also tried with install globally but its not performing click. just launch the app.But script working fine with 1.7.2 appium on 10.3 ios version

Appium 1.8 dmz not available on that release note .
yes i already have xcode 9.3 and appium 1.8 (Globally installed by npm) but still not working.
For make sure the element i have to use appium inspector which can be use in dmg

I had an issue with Appium 1.8 version after completing the tests in the result it shows test fail i think when it will try to open app again it’s browser exception.

Hi,
I tried your code in my project, but it does not work - startRecordingScreen() method does not exist. I’m using Appium version 1.8.0. What could be wrong?

Cheers, Ziga

Its not my code :slight_smile: Its the code used to test the java client.

Make sure you are using the latest java client.

Oh, I see it comes with Appium Java client 6.0.0-BETA3. Thanks

With command line 1.8 its shows error
"Returned value cannot be converted to WebElement on iOS 11.3 with Appium 1.8.0
Issues/Bugs"

13 days later

@pushpank I am facing the Same Issue(Returned value cannot be converted to WebElement) and when I tried to Down grade it to 1.6.1 It is Showing 1.6.1 in the when i tap “About Appium” from menu on the mac.When i check for Updates its saying “up to date”.Let me know if you could be able to resolve some how Thanks.

Any Idea on downgrading the Appium version so that i can run my tests without errors.

Yes, You can run on appium 1.7.2 version but iOS 11 will not work on it .

Hi,

Are those topics described anywhere else?

It sounds really interesting but it would be really great to know what exactly is improved. It’d be nice to know if I have to initiate migration from 1.7.2 to 1.8.0

just run
1.npm uninstall -g appium
2. npm install -g appium@1.7.2

3 months later

Hi ,

Has someone managed to record iOS real device execution through appium ?

I did manage to start the recording and to stop it , but when it being converted from base64 format to file with mp4 format , the file cannot be opened (getting corrupted error) - this does work for Android tough.

thanks.


No I see that the problem is with ffmpeg package

[ffmpeg] [mjpeg @ 0x7f9583000600] Found EOI before any SOF, ignoring
[ffmpeg] [mjpeg @ 0x7f9583000600] bits 103 is invalid
[ffmpeg] [mjpeg @ 0x7f9581802e00] decoding for stream 0 failed
[ffmpeg]
[ffmpeg] [mjpeg @ 0x7f9581802e00] Could not find codec parameters for stream 0 (Video: mjpeg, none(bt470bg/unknown/unknown), lossless): unspecified size
[ffmpeg] Consider increasing the value for the 'analyzeduration' and 'probesize' options
[ffmpeg] Input #0, mjpeg, from 'http://localhost:9100':
[ffmpeg]   Duration: N/A, bitrate: N/A
[ffmpeg]     Stream #0:0: Video: mjpeg, none(bt470bg/unknown/unknown), lossless, 10 tbr, 1200k tbn, 10 tbc
[ffmpeg] Stream mapping:
[ffmpeg]   Stream #0:0 -> #0:0 (mjpeg (native) -> mjpeg (native))
[ffmpeg] Press [q] to stop, [?] for help
[ffmpeg] Cannot determine format of input stream 0:0 after EOF
[ffmpeg] Error marking filters as finished
[ffmpeg] Exiting normally, received signal 2.

Any one have a solution for it ?

Thanks