App rejected due to watchdog timer timeout by apple But didFinishLaunching does not take too long


I know there are tons of questions about the same issue but most of the answer relates to blocking the UI and main thread for some calls made in didFinishLaunchingWithOptions method.

I tried to run timer instrument for my application, and debug my code(device & simulators). On the first launch of the application, it takes around 11 seconds to pass splash screen, but when I debug my code, it takes around 8-9 seconds even before executing the first line of code in didFinishLaunchingWithOptions.

So it seems like my appDelegateMethods at total takes around 2-3 seconds allow app becoming responsive, which seems kind of fair.

Also after the first launch when I try to run my app with or without timer instruments, it takes around 4-5 seconds to become active.

So my question is: Why my app takes around 8-9 seconds on first launch to get to didFinishLaunchingWithOptions method?

I also don't have anything in willFinishLaunchingWithOptions method.

Do you have any ideas? Or do I miss somethings here? Thanks.

- - Source

Answers

answered 1 week ago Misternewb #1

I believe that you may have problems with dynamic libraries load time. You may check this problem by adding environment variable DYLD_PRINT_STATISTICS to your scheme and checking your console output after launch.

settings

comments powered by Disqus