I realized an app for iOS. It all goes well, works like a charm... until the device is restarted! When I manually close the app (for example, on my iPad I slide four fingers upwards, visualize the menu showing the app "alive", hold the icon of the app and press the red badge, terminating the app) and I try to open it again this is what happens to me:
First the app remains stuck on the last page visited before closing the app (I cannot tap buttons on the tab bar or do anything else)
Then, the only thing I can do is tap the Home button and try to open the app again
At this point all I get is a perfectly black screen
The restart seems to be not a real restart, or not to be clean. This is totally meaningless to me. Am I missing something?
EDIT :
Remove your application by press Hold down Application iCon From simulator/device
And then re-install app. and check it worked or not ???
If your view display with black screen then give it backGround Color redColor or as u wish.
Its iOS app natural behavior only.
When you press Home button on device, While running any iOS app it goes in background but the The app is still in background and its save application's state.
So if you Tap agin app's icon you will get the last screen where did you leave it.
Now, if you want to Restart the app from initial you need to clear it.
Go this way.
Just double press device's Home button you can see running apps on bottom like this
For delete particular app, you simply press and hold, you can see red (-) icon on app
just click on that and you are on way.
Now press Home button and Go to Start app!!
The problem is that Xcode, when it runs an app, attach to it a debbuger which prevents it to close normally and causes problems in the reopening. Thank you very much to this guy who pointed out the problem: https://stackoverflow.com/a/15176137/1272105
Related
I've started with PWA, I want to add home screen icon to my app, but it's added to apps menu instead of home screen
It's usually added to BOTH app and home screen.
But many times it will place the icon on the second home screen for me.
Even if there is a spot open on the first.
I am building iOS app for promo. The client asked that people using it should never quit it, so I got an idea.
When people are trying to quit, they would be asked to enter the password, otherwise it's impossible. Is there a solution to this?
I would appreciate any help, thanks!
Here are the steps to easily disable the home button :
Launch the Settings app from the Home screen of your iPhone or iPad Tap on General.
Scroll down towards the bottom of the screen and tap on
Accessibility.
Under the Learning section, tap on Guided Access.
If it's not already, turn the toggle next to Guided Access to the On
position, then choose a passcode.
After having deployed your application on the device, open it and triple tap the home button.
Set your options and then tap on start.
You can leave the guided access mode by triple tapping the home button again, it will ask you for the passcode you set before.
Here is a link for more details (and illustrated with photos)
What you are doing is not possible I guess. See for quitting any app the user can simply press the big quit button on the ipad or iphone and then the app would go into the background nevertheless.
You can't prevent the user from quitting. If you try to prevent it, the OS will terminate the app directly. With iOS 4.0, you can have tasks that are allowed to complete in the background.
Check this out.
For an overview about running tasks.
I need to show the exit confirm dialog when user pressing the Home button. If yes, need to exit the application.
Is it possible to show when pressing the Home button?
This would probably cause your app to be rejected
From the Apple HIG:
Always Be Prepared to Stop
iOS apps stop when people press the Home button to open a different app or use a device feature, such as the phone. In particular, people don’t tap an app close button or select Quit from a menu. To provide a good stopping experience, an iOS app should:
Save user data as soon as possible and as often as reasonable because an exit or terminate notification can arrive at any time.
Save the current state when stopping, at the finest level of detail possible so that people don’t lose their context when they start the app again. For example, if your app displays scrolling data, save the current scroll position. To learn more about efficient ways to preserve and restore your app’s state, see “State Preservation and Restoration”.
I'm not sure you can stop the app from terminating or going into the background. You can tell it is about to go background through the app delegate applicationWilResignActive or be terminated by applicationWillTerminate.
If I press the home button and then re-launch the app, after around 10 times, the application showing splash screen and stuck for a few seconds or even crash.
There's a reason that could happen?
(The app is configured to background)
I found the problem.
I use mbprogresshud's third-party code.
And I found a mistake, this code include registration to UIApplicationBecomeActiveNotification
and this registration happens again whenever this notification recieved.
so, Caused stack over flow after several time that application move to the background and reopen.
Thanks about your answers.
I am working on a small project and my query is i have a view which displays the map and prompts me to use my current location.
my query is that when i press allow or dont allow button of the pop up it relaunches my app displaying my splash screen and then takes me back to my mapview.
So can we stop this from happening and does anyone know why this happens.
Thanks in advance.
As said in the comments, this "question" is hard to answer. Here's a try:
The popup is actually not shown by your app, but by iOS. Upon return of the popup, your application delegate's -applicationDidBecomeActive will get called. Apparently you (or the person who wrote the code for you) takes this as a sign to launch your splash screen. Of course, this should only happen when coming from the background or on startup.
So my guess is that the app is actually not relaunched at all. Put some logging in each of the application delegate functions, to see when and in what order they are called.