Inspector Crash?

[Simon Howlett]

Hey Guys. 

I am attempting to do some proof of concept for Appium, using python for writing tests for both iOS and Android. Having some success, but it seems the inspector crashes pretty much on startup if no app package is selected in the UI.

After this, trying to launch appium from either the server ui or cmd line gives me - 'error: Couldn't start Appium REST http interface listener. Requested port is already in use. Please make sure there's no other instance of Appium running already.' - and (no doubt there is a way to combat this i dont know) resolves in a need for a reboot. Given the lack of an app specified when i see this, i suspect its intended, buy having to reboot is a pain..

Also seeing some inconsistencies in recognizing elements between running with the UI open, and from command line, anything i should be watching out for?

The error OS-X gives me from the inspector is below...

Process:         Appium [175]

Path:            /Applications/Appium.app/Contents/MacOS/Appium

Identifier:      com.appium.Appium

Version:         1.6.1 (???)

Code Type:       X86-64 (Native)

Parent Process:  launchd [148]

User ID:         502

Date/Time:       2013-04-30 20:01:37.884 -0700

OS Version:      Mac OS X 10.8.3 (12D78)

Report Version:  10

Interval Since Last Report:          35891 sec

Crashes Since Last Report:           6

Per-App Crashes Since Last Report:   5

Anonymous UUID:                      F28D7473-F169-8769-B763-755A0741277E

Crashed Thread:  12

Exception Type:  EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'data parameter is nil'

terminate called throwing an exception

abort() called

Application Specific Backtrace 1:

0   CoreFoundation                      0x00007fff84870b06 __exceptionPreprocess + 198

1   libobjc.A.dylib                     0x00007fff88a213f0 objc_exception_throw + 43

2   CoreFoundation                      0x00007fff848708dc +[NSException raise:format:] + 204

3   Foundation                          0x00007fff83b48c61 +[NSJSONSerialization JSONObjectWithData:options:error:] + 67

4   Appium                              0x000000010414216c -[AppiumInspector populateDOM] + 236

5   Foundation                          0x00007fff839fbcd2 __NSThread__main__ + 1345

6   libsystem_c.dylib                   0x00007fff87e817a2 _pthread_start + 327

7   libsystem_c.dylib                   0x00007fff87e6e1e1 thread_start + 13

 

[bootstrap online]

On Tue, Apr 30, 2013 at 11:06 PM, Simon Howlett <simon....@webfilings.com> wrote:

Requested port is already in use

Try killall -9 node

[Dan Cuellar]

As bootstrap says, when Appium.app crashes you may have to kill the node process that actually runs the appium server. As for Inspector. Right now it requires that an Appium session exist with your app by either using the prelaunch simulator option in preferences along with App Path + Launch Activity and Package (Android only)

I'm working on getting Inspector not to let people launch it when it cannot run. but until then you have to be careful.

[Simon Howlett]

Thanks to both of you, that helps with that issue a lot.