iOS TestFlight: Crash on exit with v2.0.7

[JanOwiesniak]

Whats the issue?

We started our project with v1.10.1 and upgraded until v1.11.7 without any issues in the past.
Our project is on v2.0.7 right now. We followed the upgrade guide but we are experiencing crashes on most of our iOS test devices (6s, 7, 8, 11) when user hard closes the app. This is happening all the time on the previous mentioned devices but only sometimes on a iPhone 12 Pro.

The crashlogs pointed us to your library.

This is only happening when when the iOS App is distributed via TestFlight. It is not happening when i connect those devices to XCode and deploy the app.

I deactivated Unity code stripping and XCode optimizations as well to ensure it's not related to minifying (as someone mentioned in the Unity Forums) but this did not fixed it.

We also tried to remove this line from UnityCleanupTrampoline as mentioned here (without success) because further stack traces pointed into this direction (which indicates a memory leak when closing Unity)

 [_UnityAppController window].rootViewController = nil;

We downgraded back to v1.11.7, distributed via TestFlight and tested again.

The error is gone.

This whole thing seems to be related to 2.x + TestFlight.

I hope this information helps you to fix this issue.

[MorrisRH]

I've reproduced this, will get a fix in hopefully for the next release (2.0.8).

[JanOwiesniak]

Good to hear that i'm not the only one where this is happening.

Can you provide me with a hotfix? We need to release a major update of our software by the end of the week and this issue is certainly a blocker for us. Downgrading to v1.11.7 should only be last option here.

Can you tell me if this is happening for App Store versions as well or is this message a TestFlight feature only?
Never seen it before.

[MorrisRH]

Fixed, it will make it into the next release which is due later-today/tomorrow.
The crash will be in all versions, however I'm pretty sure that message is TestFlight only.

[MorrisRH]

2.0.8 is now available

[JanOwiesniak]

Hey @MorrisRH, thanks for the fast fix. v2.0.8 fixes this issue for me.