Open ghost opened 5 years ago
@vikas-thange-twc Local testing is meant route traffic from BrowserStack to your servers through your network. Whereas IP geolocation is meant to route traffic from BrowserStack to yours servers through servers from other countries. So, logically these two features can't co-exist. Supposingly even if we allowed these two features simultaneously the IP address accessing your servers would be your network IP, because of Local Testing. And hence we don't allow local testing with IP geolocation. We currently don't have a feature where BrowserStackLocal spoofs your IP address.
I hope this answers your concern.
Summary
BrowserStack recently release new feature IP geolocation is great option to test website by IP spoofing for different regions. (e.g. GDPR testing) but BrowserStack local doesn't work with
browserstack.geoLocation
capability.Expected Behavior
if browserstack.geoLocation capability specified then we expect the network traffic simulation by IP spoofing through local network.
Actual Behavior
All network calls passed without local network as a effect, The http://localhost:XXX is not reachable
Steps to Reproduce the Problem
Test1
browserstack local arguments
./BrowserStackLocal --key XXXXXXXXXXXX --force --forcelocal --local-identifier Test1
Platform details