Troubleshooting

@user17747260297 We've already let our development team know about this issue, and they will be correcting it in a future update.