Im working on an IOS app in 7.1 using APNS. I get the push
notification successfully, however it never seems to launch my app
after I "Slide to View". APNS works successfully when app is in "Active"
state, and even when the device is still lit but at the home screen (no
apps running except in background), it will launch and go to the screen i want.
From everything Ive read, this should enter at 'didFinishLaunchingWithOptions'
Ive tried running the app in XCode, then hitting the home button and waiting for
the screen to timeout and go blank, then pushing a notification to see if I could
breakpoint it but that didnt work either.
Suggestions? or better way to debug this?
Any help is appreciated.
Thank you!
Turns out this is not a problem. Text messages behaves this way already.
I had thought that it launches the app but it does not, it only opens to
the home screen. Not an issue now.
Related
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 are working with a developer that is having a hard time debugging an issue so I thought I would post here.
When we receive the build and install the app it will work fine, but after the app being in the background for a few days when we tap on the icon it will show the loading screen and then crash.
When tapping the button twice we will see the app in the background and when we bring it to the foreground it is frozen.
The same similar issue happens if we install over a previous build it crashes upon initial launch.
One of my developer friends said it might have to do with the auto login. We have Crashlytics setup but it's not catching these crashes. Does anyone have any ideas of what this could be?
Im having problems with Xcode timing out to installing the app on my device. The problems persists even if using different devices. Usually 4/5 tries will result in a black screen.
Xcode says successful and the app opens up on the device, but the screen is completely black and the device stops responding.. only a hard reset works.. the home button isn't responsive.
You can however hear that someone is calling you, but you cannot answer the call.
I have no idea of whats wrong, because it builds completely fine.. Any idea on what might be wrong here?
The error Im receiving is:
error: failed to launch '-- timed out waiting for app to launch
Update:
Someome mentioned to me that it might be a faulty cable, but I get the same black screen when downloading the uploaded app from hockey app.
Often this is the result of building the app in debug with an ad-hoc or release configuration. There was also a bug early in Xcode 5 where it would hang as well, I think this is fixed in the most recent update.
I have an app that has the UIApplicationExitsOnSuspend info list property set to TRUE.
And now I am noticing a curious issue.
I start up the app and let it run on my phone and do not touch my phone. Eventually the phone screen goes dark and the phone goes into standby mode. When I wake the phone up, what I see is a screenshot of the last screen displayed on the app. (This seems according to spec, since the Apple documentation says that in the process of moving an app to the background, ios takes a picture of the app and uses that for transitions when the app comes back to life). If I double click on the home button to see running apps, I do not see an instance of the app running. (again, working as intended since UIApplicationExitsOnSuspend is set to true).
My question is, how do I make sure that when the phone wakes up, it comes back to the default home screen and not the picture of the app ? Clearly the app is not running on waking up, so there is nothing I can do from within the app that will refresh the screen. I could try to exit when the app is going to background, but then apple guidelines say, never exit programatically!!.
Any ideas ?
You misunderstand what is happening. If you enable UIApplicationExitsOnSuspend, this means your app will terminate when normally the app would go to the background. If you run your app then let the phone sit idle until the screen goes dark, your app is still in the foreground so it is not terminated. When a device goes into standby mode, the current app is still the current app. When you wake the device, you are not looking at snapshot of your app, you are looking at your running app. Double-tapping the Home button at this point doesn't show your app because your app is the currently running app.
Your app will be terminated if you return to the home screen or switch to another app. But it will not terminate just because the device went into standby mode.
If you want your app to return to its main screen when the device is woken up, then you need to put code in the UIApplicationDelegate applicationDidBecomeActive: method to reset your user interface.
Currently working on an application and when run on the simulator or device behaves normally. When you close and reopen the application is behaving strangely.
For example I want to upload the application on the device (iPad), the first run everything is proceeding normally, then I close the application and it is open in the background and behaves strangely, cells no longer have same order.
If you delete the application and run it again after the device from Xcode everything returns to normal.
I tried both ways: Release and Debug.
I checked the code and did deallocate.
Can someone help me with more advice? Thanks in advance!
I suppose you mean pressing the Home button when saying "close". iOS transforms your app in a special suspended state and it seems you don't restore from it correctly. iOS sends a applicationWillEnterForeground notification when your app is being restored from the suspended state and you may need to behave differently than app being launched the first time.
Here you can find more info about this method.