Crash After App Brought to Foreground: Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: Window container should not be nil

Question

Created Apr ’22

Replies 1

Boosts 0

Participants 2

After updating my app, I'm now getting crashes when the app is brought to the foreground. On initial launch all appears to be fine. But when I background/foreground the app I get this:

Window container should not be nil.

Unfortunately this is only happening on production release and I cannot reproduce the issue in the debug environment.

I updated GoogleMobileAds to the latest version. I think the framework may be responsible. Curious to know if anyone else has experienced this and knows what could possible be the cause.

Answered by Frameworks Engineer in 710610022

That does not look like an exception message from UIKit, so I don't really have any specific comments on this issue – given you mention updating GoogleMobileAds you might consult with them to see if they know what might cause this

Boost

Answer 1

Frameworks Engineer OP

Apple

Apr ’22

Accepted Answer

That does not look like an exception message from UIKit, so I don't really have any specific comments on this issue – given you mention updating GoogleMobileAds you might consult with them to see if they know what might cause this

0