iPhone App Close immediately after launching - ios

I have an iPhone app and working fine . But some of(2 or 3) my customers arises a complaint that they are having issue opening the app in the iPhone . They have installed the app and when open the app it just closes out right away. Also tried restarting phone but it still does this.Also tried to delete the app and then reinstall it but this still happens.
Is this any thing i can do in my app to prevent this ? Or how they can solve this problem ?

Is there any more information you could give regarding the nature of the crash? Have you recreated this scenario in Xcode and gotten an error message?
The best I can think to tell you is to look in the app delegate. That is where your app looks first, so there is some kind of uncaught error happening.
Maybe the app is trying to use some piece of data right at launch and it's not there. Maybe you are trying to use something before it is initialized.
Is your app using any 3rd party frameworks right at launch? If so, maybe something changed with the library.
If it is happening on some iPhones and not others, perhaps you are using some framework or function that is not compatible with an older version of iOS.
Perhaps there is something in common among the kind of devices the app crashes on.
Another thought, does your app ask for any permissions? Such as using the user's location. If it does, and there is a spot in your code where you assume you have permission and you don't perhaps that could cause a crash.
Hope this helps.
P.S. just read the comments to your question. They have some good advice. I would try what they are suggesting.

Related

Why does my iOS app show it needs "Local Network" permission?

In the iOS Settings app, my app has a list of permissions it needs. It also has one that it doesn't - Local Network.
I disabled that and it runs fine, so I know it really doesn't need it (besides the fact that I never use it).
So how did iOS get the idea that my app needs it?
(The app is built with Xamarin.iOS if that makes a difference.)
With no related change to the project, that disappeared.
I assume it was something in Xamarin.iOS and was removed with some update.
So if you're facing the same issue, perhaps the latest update might help you.
Assuming that you know your code and that there is nothing relevant there, then you have used some package that causes this. There is no third possibility.

Xcode error maximum app limit reach when trying to run app on my iPhone

This is one question I am searching for all over the internet, got a lot of results but not for my situation.
As I don't have any apps installed on my device I didn't know how to solve this problem.
What should happen:
- Xcode should install the app for testing camera features I am implementing
What actually happen:
- Xcode fail to install the app saying there is more than three apps installed
As I was about to ask this question, I found somewhere that if I have some apps with the cloud symbol on them like they are in "suspense animation", as I like to call it, you need to delete all apps with this cloud symbol (because you don't use this apps so often they just get partially deleted from your device, meaning you have short storage)
So I am posting this because maybe is the same scenario for a lot of fellows here and could be something to try!
I hope this may help some folks!
Cheers mates!

Apps using firebase crash after 3-4 days of installing them on a device/simulator (iOS)

I am somewhat new to developing apps for iOS and I have been creating a few demo projects in Xcode. My problem is the following:
I have been following a few tutorials from Udemy.com and I created an app using firebase, the app works fine for about 3-4 days of use. But after more time passes by, the application does not launch on my device or the simulator. I thought I must have done something wrong when I did the tutorials, so I did them again but the same thing happens after 3-4 days of installing the app. They immediately close after I try to launch them. However, they do work if I rebuild the app on my phone or on the simulator. I do not seem to understand why this happens. has anyone else come across this problem? Or is this a normal thing that happens until you upload the app via the app store? Thank you guys, hope someone here knows. Cheers!
in such case you can check your GoogleService-Info.plist file or get idea about what's wrong by check the App terminate reason printed in your output Console.

App stuck on loading screen - no crash

I'm here because I'm totally jammed on a problem, and I need some suggestions of where to look for an issue. I submitted an update to my iOS app, and when users try to update the app, the app no longer goes any further than the splash screen. They have to uninstall and reinstall the app for it to work properly.
I've testing the upgrade locally through xcode, and I tested it using TestFlight, and can't reproduce the behavior in either case. Does anyone have an idea what this could be?
Edit
I should also add, there is no crash. It just hangs there.
Did you use Local database in app, previously?
if yes then migration is required, if you make changes in Database.
i think it maybe issue.

User suddenly can't get past launch image screen

A user has reported that my app suddenly won't launch on their device. They sent me a video, and they launch the app, the launch image screen shows for a split second, but then crashes back to the iOS home screen.
The user tried deleting and reinstalling the app with no benefit.
I use Crashlytics, and am not getting any reports of crashes from them (or any other user- although I've seen them in prior versions so I know it's working correctly). I'm also not seeing any crashes in iTunes connect.
I asked the user to send me any crash reports in the Settings Diagnostics section and they said there are none listed for my app.
I have confirmed that their iOS version is supported by my app. (iOS 8.4).
I'm not sure where to go next, and would appreciate any pointers. Sorry for the vague question but I have posted everything that I know about the situation.
Just wanted to provide some closure on this. The user ended up wiping and restoring their device, and it solved the problem. It seems extreme to me but it was their own suggestion and didn't take them long to do. So I'm not sure what caused this but that's one (albeit brute force) way to fix it.

Resources