When PEBBLE_PHONE env. var is set in .bash_profile, pebble install --emulator basalt still connects to PEBBLE_PHONE ip address

[tkafka]

See https://forums.pebble.com/t/since-sdk4-0-i-cant-run-emulator-again-once-it-has-quit/23792/2

$ cat ~/.bash_profile

...
export PEBBLE_PHONE=192.168.0.12
...

$ pebble logs --emulator aplite

Connecting to ws://192.168.0.12:9000/ ... (instead of localhost:xxxxx)
(logging in libpebble2/communication/transports/websocket/init.py constructor)

This is a regression from 3.x where the same setup worked fine for me.
Two evenings of my life gone :(.

[tkafka]

Update: this happens only when export PEBBLE_PHONE="192.168.0.12" is in my .bash_profile, when I just run PEBBLE_PHONE="192.168.0.12" in my bash shell, pebble-tool works ok.

Is it possible that pebble-tool spawns a new environment when running the emulator and then prefers it to the command line parameter?

[Katharine]

This isn't an environment issue; a connection handling refactor inadvertently changed how options are prioritised such that the phone environment variable beats the emulator option.

All subprocesses ignore environment variables, and so would not be affected by the state of the environment.