• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Delays in awaking iOS app
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Delays in awaking iOS app


  • Subject: Re: Delays in awaking iOS app
  • From: "Gerriet M. Denkmann" <email@hidden>
  • Date: Tue, 04 Feb 2014 12:50:35 +0700

On 4 Feb 2014, at 01:35, Matt Neuburg <email@hidden> wrote:

> On Fri, 31 Jan 2014 15:09:37 +0700, "Gerriet M. Denkmann" <email@hidden> said:
>> The real problem is:  iOS 7 ignores the first tap (if it comes too soon after applicationDidBecomeActive: - "too soon" meaning: less than about a second).
>> Whereas iOS 6 records and processes all taps.
>
> I've noticed often, just in my ordinary iOS 7 life, that there is a problem with the system's handling of the showing and removal of the snapshot image (taken when the app was backgrounded and displayed as the app is reactivated). It takes a _very_ long time for this image to be replaced by the real interface, and meanwhile the app is not responsive because you're not _in_ the app: you're tapping on the snapshot. I wonder if that's what you're experiencing. m.

My test app has a UILabel (called lastLine) at the bottom, and a button ("Tap Me") below it.

In applicationWillResignActive: I do:
	rootViewController.lastLine.text = @"#####################################################";

In applicationDidBecomeActive: I do:
	rootViewController.lastLine.text = @"Now!";

I start the app on iPad
Put the iPad to sleep.
Wake the iPad.
"slide to unlock"  (now I see "#############" getting changed to "Now!" after a fraction of a second)
When I see either: (A) "Tap Me" or: (B) "Now!" I tap the button 4 times.

In case (A) only 3 button hits get recorded.
In case (B) all 4 button hits get recorded.

The button hits are spaced by about 0.2 seconds.

This seems to imply that when the applicationDidBecomeActive there is a time of about 0.2 seconds, where it LOOKS responsive, but really it is NOT.
Maybe what I see is just (as you suggested) the "snapshot image", not the real test app.


In a real app the following happens:

applicationDidBecomeActive
I see an obviously functioning button and tap it.
Nothing happens.
After about a second I realise something is wrong and tap the button again.
Now I get the expected reaction.

I curse the app, because the button is unreliable.


None of these problems occur with iOS 6.


Kind regards,

Gerriet.


_______________________________________________

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


References: 
 >Re: Delays in awaking iOS app (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: Mismatched viewWillAppear/viewDidDisapper calls possible?
  • Next by Date: Managing image loading
  • Previous by thread: Re: Delays in awaking iOS app
  • Next by thread: Re: Mismatched viewWillAppear/viewDidDisapper calls possible?
  • Index(es):
    • Date
    • Thread