After iOS 8 release, we are getting feedback from some users about our app that whenever users try to start app, operating system navigate it to background. I was able to examine this issue myself and I see that OS does not terminate app or app does not crash. In fact, app appears in background apps menu. Whenever user tries to open the app it closes itself something as if “simulating user's home button touch”. Of course, I’m not doing something like this by code. And this issue only show 100 in 1 and only in iOS 8 devices. It shows any kind of devices from iPhone 4S to 5S.
Have you ever encounter an issue like this?
Related
hi i have an iOS app that runs perfectly in when i run it through Xcode on my iPhone.when i press the home button and lock the screen, the app keeps recording the data.after 1 or 2 hours when i unlock screen it is still recording data and works perfectly.but when i stop the app , unplug my phone and run the installed app directly through app icon on my iPhone it is killed by the os after a few seconds in lock screen.i have already asked similar question but couldn't find any help.if someone could download the source code and have a look at it it will be very nice of him/her.Thank you
why my Ios App is killed by OS in background mode?
The OS won't allow apps to run for long periods in the background in order to save power. There are exceptions — you can tell the OS that your app needs to run in the background for one of several reasons such as playing music in the background. There are also some facilities for waking up your app in the background to do some processing -- for example, your app can be notified when the location changes.
I am currently prototyping an iOS iPad app for my company. Before I go in the details of what I am trying to do, this will be an enterprise app deployed by a local MDM. All the iPads that will have the app installed are supervised with a mobile config that allows the app to be in autonomous single app mode. So far, everything is working fine. The iPads are not (and cannot) be jailbroken.
I am looking for a way to basically switch the app to the foreground whenever the iPad is unlocked. I am aware of this thread (ios open app after screen unlock) from 2013, and I am hoping that 5 years later a solution has popped-up. Since our app is an enterprise app, it does not have to respect the app store requirements. I can successfully detect lock events if the app is opened when the device is locked, but when the app is not in the foreground, I would need it to be awaken from an iPad event.
The basic idea is that whenever the iPad would be unlocked, the app would freeze the iPad in single app mode, and the user need to perform some action inside the app to "reenable" the iPad and disable single app mode. If a user can re-lock the iPad and bypass the app (even if he successfully accessed it once) it's a no-go for us.
Edit
I am trying to awake the app after the unlock of the device. Basically once the iPads is unlocked (after pressing the home button) the app would be started automatically.
That is a loaded question but you could lock the ipad to only use one application with "Guided Access" There is a walkthrough here.
Here are the first steps:
Open “Settings”
Go to “General” > “Accessibility”
Tap on “Guided Access” (Scroll down the page a little, it’s under
the “Learning” section)
Flip the switch to “ON”
Tap on “Set Passcode” (this will prevent
users from leaving “Guided Access” mode)
Enter a passcode
Launch your App
With your app still open, triple-click the Home button
Whenever i have my app open, then lock my screen, the app closes if the screen is locked for more than 5 minutes. So when I unlock the phone again, I am at my home screen and have to re-open the app.
This happens on both iPhone 6 device and simulator. However, if I build and run the app using the debugger, it doesn't happen, which is making it difficult to fix.
I'd appreciate any suggestions that might point me in the right direction.
When my app is running on simulator and I press the home button it enters the background properly. But when I put the app back in the foreground, it has apparently dropped all the managed objects in memory, and the app crashes when I try to resume using it. There's no code in the any of the callbacks for the app changing state that would cause that, and the app has never displayed this behavior before.
What changed was going to xCode 6 / iOS 8 on the simulator, and I also applied "Reset content and settings" in response to this problem.
The app behaves problem-free on actual devices, both iOS 7 and iOS 8. Is this another bug with the new iOS simulator?
If you did "reset content and settings" with the app in the background, you probably blew away all its context. You should terminate the apps in the background before running that.
We're developing a web app that extensively uses Cavas 2D for some demos, and is successfully running on both iOS and Android devices. Recently we've added stand-alone mode for iOS devices, so user has to "Add-To-Home-Screen" and run it using screen icon, just like regular app.
What happens recently is that after 10-12 times we start the web app on iPhone4:
Status bar (initially set to 'black') suddenly turns white and we cannot exit Safari (by pressing home button).
If we try to make screen shot (home + power button), shutter sound is played as if screen shot was taken and saved.
If we try to lock the device (power button), screen turns black, but no action after that can bring unlock-screen or any screen for that matter - display remains black.
We can only do reset by pressing home + power for 10 seconds after this point.
If we do not lock the device, web app continuously work with no issues at all, it does not crash, but cannot exit it (double click on home button also has no result).
Has anyone experienced this with their web apps?
Any guidance in how to debug this would be highly appreciated. We've tried using Safari on OSX, connect iPhone to it and use Develop -> iPhone menu but no luck so far.
Thanks in advance!
I would start trying to debug by running XCode with the iPhone connected to the computer.
In XCode open "Organizer" and go to the tab "Devices".
You should see your device there, from which you can view the iOS console. That might be able to tell you what is going wrong with the phone stops responding.
I don't think you have to put the phone in development mode (or be a paid developer) to see the iOS console.