Ok thanks that's interesting as it shouldn't have passed certification if that was case. This means that it there are some hardware difference causing variation in behavior.
Anyways I believe the fixes we pushed should address that issue as well. My guess is that we tried to initialize settings before all of the UI components finished loading. On difference system specs there can be a race condition, so if the UI hasn't finished loading before the settings kick in it may cause a crash. It now waits until UI is completely loaded then applies the settings.
I just checked the publishing status it should be up on the store soon, if not already. Please keep me updated if this build fixes the issues. Thank you so much!
Anyways I believe the fixes we pushed should address that issue as well. My guess is that we tried to initialize settings before all of the UI components finished loading. On difference system specs there can be a race condition, so if the UI hasn't finished loading before the settings kick in it may cause a crash. It now waits until UI is completely loaded then applies the settings.
I just checked the publishing status it should be up on the store soon, if not already. Please keep me updated if this build fixes the issues. Thank you so much!