Summary: When flipper starts it writes to both env vars the value from settings. This is needed for subprocesses to have access to them. The problem with the check for both env vars is - In prod environment applications does not have access to them - In dev, when developers launch flipper from terminal (`yarn run flipper-server`) it picks up these env vars if they are set which can cause different behaviour in dev and prod To make flipper work more deterministic, for users and us. I removed this check and now we always write to these env vars what the user has provided in flipper settings or the default. Reviewed By: lblasa Differential Revision: D51266495 fbshipit-source-id: cf3adfd4ba83a733a30b5b0b29c270b32ff3a61a
flipper-server-core
Package that manages connections with flipper clients, queries for adb/idb clients, accepts incoming websocket connections and takes care of certificate exchange.
Used by Flipper desktop, flipper-server and flipper-dump