Thank you for the log, we believe we have found the issue. We are aiming to have this fixed for the 3.5 app release.