Update transport.js

[Topperfalkon]

Appium can get upset if you supply both a browserName and an appPackage as desiredCapabilities at the same time.

A brief reading of an Appium issue report from a few years ago suggests it shouldn't complain, but this will fix the current behaviour to allow users to set a null browser

Thanks in advance for your contribution. Please follow the below steps in submitting a pull request, as it will help us with reviewing it quicker.

Should resolve an issue raised in discussion #2881

[CLAassistant]

All committers have signed the CLA.

[beatfactor]

Thanks for submitting this. Does this cover it?

[Topperfalkon]

Yeah, turned out a lot simpler than I thought 😄

So, now, if you pass through browserName: null, in your suite's config, this should just pass all the way through without error. Before it was falling into the browserName.toLowerCase() operation and erroring.

I had a brief look at the v2 branch and I think that'll have a similar problem, but that area's changed quite a bit so I haven't attempted a fix on that branch

[Topperfalkon]

@beatfactor do you need anything else from me on this one? It seems to just be waiting for another reviewer

[beatfactor]

A small test will be needed. I'll merge it in soon.