Hello all,
Doing some forum clean-up this morning - this bug was resolved with the release of Local v6.2.0 on January 19th. Local v6.2.1 is the latest stable, and Local v6.3.0 is in beta if you would like to test it.
I will mark this issue as resolved, but let us know if you run into anything similar after updating.
Thanks,
Austin