Skip to main content

Only applicationWillResignActive called when iPhone shuts down?

Image
By User


Hallo experts,



I've tested what's happing with my app when the iPhone is switched off while the app is active. For this purpose I logged the callback methods of the app's lifecycle in the xcode debugger console.



The result was: When I press the on/off button of the device for some time applicationWillResignActive is called. The iPhone shows an option to switch off the device on the screen. If I ackknowlege to switch off, the iPhone shuts down. But apperently no further callback methods like applicationDidEnterBackground or applicationWillTerminate are called . As result all data would be lost if I don't save it in applicationWillResignActive . Although the iOS Application Programming Guide says, one should save an app's data in applicationDidEnterBackground and applicationWillTerminate .



What do you think, is one of the two methods still called and is only not printed in the console anymore?



Best regards


Source: Tips4all, CCNA FINAL EXAM
Labels:

Comments

  1. UserMay 14, 2012 at 9:17 AM

    I think that your test is probably correct. The app is no longer active yet it has not gone into the background -- kind of like when I call comes in -- so I think the notifications make sense.

    What should you do about it? My suggestion would be nothing. It seems to me that this event happens so infrequently that it's not worth worrying about. If you want to go belt and braces then saving state in ‘applicationWillResignActive‘ should work as long as there's not much to store.

    ReplyDelete
  2. UserMay 14, 2012 at 9:17 AM

    I've made some further tests:

    I've saved the called lifecycle methods in a database and turned off the iPhone while may application was running. Actually only applicationWillResignActive is called.
    But after the shut down my application resides in the state "not running", because launching it initiates calls of application:didFinsihLaunchingWithOptions: and applicationDidBecomeActive. So the application data is lost if I don't save it in applicationWillResignActive.

    If the battery is empty while an application is running applicationDidEnterBackground and applicationWillTerminate are called (no call of applicationWillResignActive!).

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月１０日ごろ＝韓国

By Unknown
Post a Comment
Read more

div not scrolling properly with slimScroll plugin

By User
I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?
1 comment
Read more

Why does this javascript based printing cause Safari to refresh the page?

By User
The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
5 comments
Read more