Appium server v1.2.3 released

Should we expect complete iOS 8 support in 1.3 or the 1.2.3 has any little support for iOS 8 we can play around ???

Tried running with xcode 6, complains about the tracetemplate path

WebDriverException: Message: u'A new session could not be created. (Original error: Could not find Automation.tracetemplate in /Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate)

Fix the Instruments path. They changed the .bundle folder to .xrplugin

ln -sf /Applications/Xcode6-Beta2.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.xrplugin/ /Applications/Xcode6-Beta2.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.bundle

Match the directory structure of Xcode 5

mkdir /Applications/Xcode6-Beta2.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/
mkdir /Applications/Xcode6-Beta2.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/

Fix the simulator app name. They changed it from iPhone Simulator to iOS Simulator (about time)

ln -sf /Applications/Xcode6-Beta2.app/Contents/Developer/Applications/iOS\ Simulator.app /Applications/Xcode6-Beta2.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone\ Simulator.app

Fix the binary name. They changed it from iPhone Simulator to iOS Simulator (about time)

ln -sf /Applications/Xcode6-Beta2.app/Contents/Developer/Applications/iOS\ Simulator.app/Contents/MacOS/iOS\ Simulator /Applications/Xcode6-Beta2.app/Contents/Developer/Applications/iOS\ Simulator.app/Contents/MacOS/iPhone\ Simulator

Hi,

Am i the only one that still has problem with the hang at:
info: [debug] Starting iOS device log capture via deviceconsole

When testing on a real device, even after upgrading to 1.2.3?

Does this mean that the old xpath issue with non compressed layout hierarchy is fixed? Would be fantastic if it was.

Is there an OSX build of 1.2.3? All I see in the downloads section is a dmg for 1.2.2.
Thanks.

Can someone in the know, please explain what this means? The answer just might resolve some issues we are having with XPath.

Should the MAC version be updated already? Mine is still pointing to 1.2.2

@jonahss

Thanks for the reply. When you refer to xpath compression, I think I know what you mean, but could you provide an example of that so that I'm clear about it's purpose?

Ok, I'll give it a try.
Android UiAutomator has a method called setCompressedLayoutHierarchy:

/**
     * Enables or disables layout hierarchy compression.
     *
     * If compression is enabled, the layout hierarchy derived from the Acessibility
     * framework will only contain nodes that are important for uiautomator
     * testing. Any unnecessary surrounding layout nodes that make viewing
     * and searching the hierarchy inefficient are removed.
     *
     * @param compressed true to enable compression; else, false to disable
     * @since API Level 18
     */
    public void setCompressedLayoutHeirarchy(boolean compressed) {
        getAutomatorBridge().setCompressedLayoutHierarchy(compressed);
    }

So.... when that is set, every single UiAutomator command runs on a subset of all the views that are actually present. That makes lookups and traversals of the layout hierarchy faster, since there's less elements to check on every operation.

I opened up the Android ApiDemos app and called getSource(). Then I set ignoreUnimportantElements to true and ran it again.

See how less is returned when the layout is compressed? A bunch of nested FrameLayout and LinearLayout views were removed since they don't seem to actually contain anything important.

Things will run faster, but if you wanted to query the hierarchy for one of the "dropped" views, appium wouldn't see it, or xpath might grab the wrong element instead. That's why it's disabled by default. I would try enabling it and see what fails.

Thanks.

This helps in my understanding. It appears that this is only supported for Android devices at API level 18 and up. So, that is certainly an important consideration if you need to test an app that supports API levels 15 - 19 (our use case).

I know, noob question, but how do I update it on MAC? The automatic update does not find it so far..

Excellent work Jlipps you really stayed on this. Much thanks to you and the forum contributors. All good so far on the simulators. Thanks

'which appium' should get something like /usr/local/bin/appium, shouldn't it?

I'm waiting for the Mac binary distribution, too, but until then I'm pleased to start Appium 1.2.3 from the command line.