Hi everyone,
The issue has been resolved - launching the app again will work as usual.
Thanks for posting a workaround, more details on the underlying issue can be read here for the curious.
