Great to hear that it is being worked on! Do we get a notification when this has been fixed? As of beta 3 there is still no improvement. However thanks for picking this up!

I also added a feedback item with the same NSInvalidArgumentException, caused by a different app listed as: FB13872901. It also might be the same problem as FB13872931.

There is no error message printed during runtime.

Unfortunately there is no error message printed at runtime.