Skip to content

Conversation

bayandin
Copy link
Contributor

@bayandin bayandin commented Dec 3, 2015

I actually don't know why it was nil before. There were no comments about it.

But now instead of Uncaught exception: status code 500 we can get clear error message from server: Uncaught exception: Could not determine your device from Appium arguments or desired capabilities. Please make sure to specify the 'deviceName' and 'platformName' capabilities (this example comes from Appium)

@titusfortner
Copy link
Member

I think this was just never added. Looks like Jari added a few that weren't implemented 4 years ago, so I'm not sure why he didn't add this one as well. The documentation for response status indicates that it should be: 'SessionNotCreatedException.' Since Error is obviously more correct for Ruby, though, I agree with this implementation.

titusfortner added a commit that referenced this pull request Dec 3, 2015
Signed-off-by: Titus Fortner <titusfortner@gmail.com>
@titusfortner titusfortner merged commit dfce195 into SeleniumHQ:master Dec 3, 2015
@bayandin bayandin deleted the rb-add-error-for-33 branch December 3, 2015 20:22
topherbullock pushed a commit to topherbullock/selenium that referenced this pull request Oct 4, 2017
Signed-off-by: Titus Fortner <titusfortner@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants