On iOS 15 we observed that calling [UIScreen mainScreen] as part of setting up device configuration resulted in the Unity test app hanging while attempting to access the main bundle. Additionally we have evidence that the thread which called [UIScreen mainScreen] was terminated before the completion of the call.
We should determine
What happens to the thread that calls [UIScreen mainScreen]? (this could be done by setting a breakpoint immediately prior to the call, and stepping through)
Does this always happen, or only when integrated in a Unity project? ('this' meaning [UIScreen mainScreen] somehow explodes)
On iOS 15 we observed that calling
[UIScreen mainScreen]as part of setting up device configuration resulted in the Unity test app hanging while attempting to access the main bundle. Additionally we have evidence that the thread which called[UIScreen mainScreen]was terminated before the completion of the call.We should determine
[UIScreen mainScreen]? (this could be done by setting a breakpoint immediately prior to the call, and stepping through)[UIScreen mainScreen]somehow explodes)