Hey everyone, and apologies for the troubles here. We’ve identified the cause of this issue in the 5.5.1 build of Local.
Currently, we are recommending anyone experiencing this problem to downgrade to version 5.4.1 in the meantime.You can download it here: Local 5.4.1
We will make sure that the next release includes a resolution to this problem!