Re: iOS watchdog timeout at startup vs later?
Re: iOS watchdog timeout at startup vs later?
- Subject: Re: iOS watchdog timeout at startup vs later?
- From: Kyle Sluder <email@hidden>
- Date: Tue, 12 Aug 2014 18:27:14 -0500
On Tue, Aug 12, 2014, at 06:24 PM, Rick Mann wrote:
>
> On Aug 12, 2014, at 15:12 , Kyle Sluder <email@hidden> wrote:
>
> > On Tue, Aug 12, 2014, at 04:00 PM, Rick Mann wrote:
> >> Hi. Is the timeout (the one that kills your app if the main run loop
> >> blocks for too long) longer during app startup than after it's running?
> >> I'm concerned about the Core Data migration my app does at startup. I
> >> will eventually move it to work on a background thread, but I'd like to
> >> punt that to the next release in the interests of time.
> >
> > Don't punt it. Do it now.
> >
> > Paul Goracke gave a very nice description of the death spiral that
> > ensues if you try to perform a main-thread migration, especially at app
> > launch: http://vimeo.com/89370886
>
> Unless we can show that it Just Doesn't Work (which it does), I seriously
> can't spend the time to do that right now.
Well in that case, be prepared for rejection from the App Store, or
one-star reviews from your customers, when the watchdog repeatedly kills
your app during launch.
Obviously I don't know your app's architecture, but conceptually, even
if you're using the thread-confinement model, you just need to throw up
some form of modal UI while you perform the migration on a background
thread.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden