Just adding to this thread that the new version of the app, v0.5.4, is certified with Apple and should no longer have this issue!
