We are testing our app on an iPad with 4.2 on it.
How do we force the app to stop. We are testing the initial load section of code and of course that only fires when the app starts up.
Reminds me of a similar issue on our Android apps....
Double-click the home button, hold your finger down on the app, and then tap the red minus sign.
Related
This Xamarin.ios app on iPhone must have no splash and no display whatsoever and must leave previous app displayed.
Is is launched by an Objective-C app and it only runs for a short time and then ends itself, leaving screen of the ObjC app always displayed
I need the app that launched it to remain in focus.
USAGE STEPS...
I open the ObjC app, which has command buttons
I press button that starts my Xamarin.ios app which should have no display at all
ObjC app button menu remains displayed
Xamarin.ios app runs and then ends itself
ObjC app button menu remains
Please help -- am under the "time gun" .
This is not possible on iOS - if it makes it easier for you you could have whole the time in this world (and not being under the "time gun") and could not solve it unless Apple changes something in future iOS releases which is unlikely.
The closest you could get to it is to record the screenshot of ObjC app before it launches Xamarin.iOS app, send it some way to Xamarin app (the best way would be if they could be the same App Group), put empty splash screen and ensure that it displays just a split of the second and then display your screenshot in the Xamarin app and do whatever you want to do.
Short description of the problem: First time when the app is opened the splash screen appears normally and than it is followed by the home screen. But after the app was closed from taskmanager (double click on home button and swipe up) and opened again, the previous(cached) home screen appears(flashing) for a very short time before the Splash screen appears. I think every iOS app running on iOS 11.4 (ios 9 and 10 not affected) is affected not just mine. As you can see below(slow motion video), I could reproduce it with the Twitter app also - firstly it opens normally and at the second time the problem appears.
My application is suffering constantly from this issue in a predictable way, but the Twitter and other apps are not. They produce this symptom every now and again but than nothing for the following 5-10 try. With normal usage - if I don't terminate the app manually or there are a few app opened between mine is closed and reopened - the problem is not appearing.
The question is, is there a workaround for this issue?
Try adding this line of code in didFinishLaunchingWithOptions:
UIApplication.shared.ignoreSnapshotOnNextApplicationLaunch()
I'm developing a libGDX game for Android and iOS (MobiDevelop's RoboVM fork). Android works perfectly, but I have a issue on iOS. When the iPhone home button is pressed to leave the game, and I launch the game again by tapping on icon, the game does not resume from where it was paused, but instead restarts, which means the loading screen is displayed, all assets are reloaded, and the main menu appears. Like a fresh/new start of the app. I do not have any specific configuration for the iOS module in my libgdx project and am using what was pregenerated.
Is it possible to tell iOS that I do not want to kill the process? I want to switch to pause/sleeping mode only.
I found a reason of this problem. I tested it on the real device, therefore I was unable to see a logs. When I switch to simulator and look at the logs, I found a NullPointerException. This was a cause of application crash. When I fix this bug, everything works as I expected. After iPhone home button is pressed, pause() method of com.badlogic.gdx.Screen is called and after rerun the game, it continues from exactly where it stops / pauses.
I learned a lesson: make a tests on simulator at first :-)
While I am entirely unfamiliar with libGDX, I can tell you that except for a few very specific cases (VOIP etc.), you cannot control what iOS does with your app when the home button gets pressed.
Furthermore, it is the responsibility of the developer to save the app's state when the app leaves the foreground since this is not something that is or can be handled automatically in a performant way.
I have an IOS swift app that I'm working on that seems to run fine. When I press the home button to exit it while running, the app icon turns grey and I can't go back into the app nor delete it. The only way tot go back is if I double tap the home button and find the app under all the running apps. What is causing this issue?
I was trying to change the app name and maybe messed up some setting because even earlier iteration of the app doesn't work so it's not a bug in code.
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.