Post

Replies

Boosts

Views

Activity

Reply to ITunes Connect - Crash report - Code 0x8badf00d
Hi,We have a similar problem with our app when responding to an iBeacon region launch. In some cases, the watchdog gives us 2.6 seconds to create the scene in background, which our (fairly large) app simply can't achieve. Weirdly, after the first launch attempt fails/crashes (bad food), iOS almost immediately launches our app again with a larger allowance and starts up successfully.@eskimo Any idea? I think it's weird that the app at first has a low allowance, and then immediately launches again with a larger allowance.(iOS 13.3, iPhone 7 with a poor battery)
Jan ’20
Reply to ITunes Connect - Crash report - Code 0x8badf00d
@eskimoThanks for your quick response!I understand that resuming the app requires less time (and thus a lower allowance) than launching the app. However, what I meant is that the first allowance (2.6 seconds) was for a (background) launch (`scene-create`) and not for resuming the app. After that first attempted launch crashed, it was almost immediately launched again with a higher allowance.> Two seconds should be more than enough to (effectively) bring up a window.What exactly is involved in bringing up the window?Is it:Returning from `didFinishLaunchingWithOptions`?Having instantiated the `UIWindow` and making it key and visible?Completing the first layout update?And when does the watchdog timer start ticking? Is that before or after the libraries are loaded?
Jan ’20