Iphone App developed with KivyMD Crashing - ios

I've created a game with KivyMD and currently I am testing it on iOS. I have tested the game on Android and it works flawlessly. The game builds successfully in XCode and once built, the game works fine on an iPhone. However, few days later, something seems to be going wrong and app starts to crash in iPhone. As soon as I launch the game, I see a black screen which appears to be a pre-splash. However, I haven't set a pre-splash for the game. If I rebuild the game in XCode again, it builds successfully with no errors and the app starts to work fine again for few more days and then it starts to crash. Can someone help me with the following?
Is there a way to look at the error message in some log file on iPhone when the app crashes?
Is there a debugging tool that I can use to troubleshoot when the app crashes?
Is there an iOS simulator app that I can use on my iMac to test the app?
XCode shows the build log as successful always. So, the app crashing appears to be a run-time error. Unfortunately, I am new to this and needs some help.
Thanks in advance.

UPDATE: You'll probably want to find a solution that is specific to Kivy. This answer may help. In fact, your question may be considered a duplicate:
https://stackoverflow.com/a/27175629/2476389
Generally, I recommend Firebase Crashlytics for crash logs. If a crash occurs in your app, the stack trace and other helpful info will be uploaded to your Firebase console the next time the app is started. You can see all your crashes in the console. You will need to follow the instructions to integrate crashlytics into your app and then release a new build, but it's well worth it. This will allow you to get crash logs from all devices (testers, users, etc).
https://firebase.google.com/docs/crashlytics
For crashes you can reproduce on your dev device, you can also retrieve the log directly:
https://developer.apple.com/news/?id=nra79npr

Related

Firebase console show this while choose Crashlytics with iOS "We'll be listening for your app to communicate with our servers"

Please guide me! Why Firebase console take much time to communicate with server. I'm waiting one and half hour to complete this takes. Anybody tell me what is the reason behind this issue or anyone facing this issue before.
Not show the Graph.
Please make your app force fully crash 2-3 times, after disconnecting your app from Xcode.
This is what worked for me.
In my case, I solved this problem by doing these steps:
Make sure you follows the all steps that mentioned in Firebase Documentation Crashlytics.
Use fatalError() for crash your app.
Uninstall App from simulator or Real Device
Run the app on Simulator or Real device then stop running.
And then Open the App that Install on Simulator or Real device.
Open Firebase Console project And Refresh it.
This can happen as a result of several different issues, however they're usually connected to your app being unable to make the proper call to the Crashlytics settings endpoint. You can either write in to Firebase support, or feel free to start a private thread with me, and I can check your apps settings in the Firebase backend.
if you followed all steps as per latest crashlytics documents!
try forcing a crash directly with button click on initial view instead of just building and running your app
use fatalError() for crash your app

How to debug react-native iOS app crashing on startup after a week or so

I started messing around with react-native. I've built a small application and it seems to work fine (package.json). I can work on it in Debug or Release mode, using the simulator or my iPhone 6S device, and all is well.
This app is just for me so I don't pay for the Apple Developer thing, and I just run the app in Release mode on my device, and it...seems to be fine? I can quit xcode and go places and the app works fine.
After a week or so, it's hard to tell, the app stops loading. It'll display the splash screen for a split second and then it's gone back to the home screen.
I setup Rollbar, but it doesn't catch anything. I look in the Privacy -> Analytics area and don't see anything there either.
I'm not really looking for an answer to my exact problem since various SO questions and other places suggest it's probably something weird and specific. My main problem is I don't know even where to look/how to debug this kind of thing. If I build the app and run it on device again, it'll run fine. I need to try to debug without loading new code, and have no idea how that works on iOS. I've tried poking around at the Debug -> Attach to Process by Name, but the app never gets far enough to do anything with that.
Alternatively, I throw react-native in the garbage and use something that works...
App provisioning with a free developer license (?) is 7 days. See: Why does my free XCode Provisioning Profile only last 7 days?
You can likely verify this by looking at error messages in the console window. Connect your device, and in Xcode go to Window/Devices and Simulators/Open Console, then launch your app.

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.

Apple's answer to my app: App rejected because it crashed but I can't find the crash

I received an App Submission Feedback from Apple:
Thank you for your resubmission.
We were unable to review your app as it crashed on launch. We have
attached detailed crash logs to help troubleshoot this issue.
Next Steps
To resolve this issue, please revise your app and test it on a device
to ensure it will launch without crashing.
I'm unable to find the crash reason, It seems like an unsymbolicated crash, which are often useless. My app doesn't crash when I test it, not even in release mode. It works perfectly in emulator as well as other real devices I have tested (Such as iPhone 4s, 5, 7 and also an iPad, iOS 9 and 10)
Here is the crash log
Please let me know if you have any idea what I can do to see what is the problem or if you know what is the problem, I would really appreciate your help, I can't submit my app to app store until this problem is resolved.
Note: The application was created with react native.
I have the same problem and rejected 2 time. My app created by React Native and have Facebook Login using FBSDK. It work fine on iOS Simulator and Testflight, but Apple reject and said it crash on startup up, they unable to test.
On the first time, i'm just rebuild, increase the version, submit again, and Apple accept it.
The second time is just yesterday and going to submit again.

My iOS app every now and then refuses to launch until I reinstall it

I've got an app that uses Core Data that sporadically stops launching so I have to reinstall it using XCode and then it launches again like normal for a while, with all the Core Data information still preserved.
I have seen that an app often stops launching when the target of an app is too low in comparison to the device software version, however this is not so for this app and device (iPhone 6s).
Have you had such an issue before? What do you think could be causing this problem?
There are many, many, many things that could cause an app to fail to launch. You need to narrow things down and collect some data so that you can find out what the problem is and do something about it. Right now you don't even know that it's related to Core Data, you're just guessing.
For a crash on launch, look at the device console and see what messages appear when you try to launch the app and it fails. You can get the device console messages by
Connecting your device to your Mac
Opening Xcode's "Devices" window (cmd-shift-2)
Looking in the bottom half of the window
A better way to watch the console is to use the free iOS Console app.
The problem was that, as mentioned by dan in the comments, the code was being signed for a short period of time (7 days) and so I had to keep re-installing it on the iOS device to keep it working. Thus to keep the app working indefinitely a paid developer account is needed.
Also mentioned in this reddit forum:
https://www.reddit.com/r/jailbreak/comments/4hotx3/news_free_developer_account_installs_reduced_to_7/

Resources