I have deployed an ionic app on my iPhone from a Xcode project. After 2 weeks, I tried to open my app on iPhone and it closed unexpectedly. Thus, today I have re-deployed the app, it can be opened successfully. However, I'm curious what is the cause and will it close unexpectedly again. Any suggestion? Thanks! :)
This issue can be with the time that cordova takes to load. If your app is heavily loaded with javascript libraries, more controllers and factories, some external javascript files(from web) cordova takes a little more time to load, if it crosses the time that it has to, the app will be closed unexpectedly.
Same way in Android, you will see the error "{AppName} stopped unfortunately".
I found that it is just because I use a free Apple developer account. The app can run only about 7 days. If you want a long term app, you need to pay for it.
Related
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
I have two completely different Ionic apps running on my iPhone and I can get one to open the other and visa versa!
First app, App-V3, is an Ionic V3 app that has been in production for years and has been downloaded for App Store. Second app, App-V4, is an Ionic V4 app that is still in development and loaded onto my phone with Xcode. The code bases are completely different as are the back-ends and remote databases.
Procedure: both apps have been stopped, i.e. will restart, display launch image, to open.
Either app - start, wait for launch image to come and go, and then the app becomes live.
Close this app using home button on my iPhone6S.
Then immediately open the other app.
The correct launch image displays but the original app appears!! The order makes no difference, start with App-V3 or App-V4, will have that app running in the other with above steps.
This does seem to be time dependent. After opening one app, after that app becomes live, if I wait for approximately 6 seconds or more, then close it, and immediately open the other app, then this app will start correctly. It seems that if I wait for only 5 seconds or less, then I will see the issue.
I would like to understand why this is happening. Thanks.
Maybe you have the same Id in the config.xml of your both projects, I know in android wont let you install it if its the same.
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.
A couple of years ago I wrote and debugged an Apple Watch app using the watchOS 1 SDK. I am now working on a new watch App using the watchOS 3 SDK.
The Watch App part is able to be debugged. I can set break points and step through it. However, I use the WatchConnectivity framework to get information from the iOS app. This isn't working and I'm unable to debug it.
When I run the WatchApp scheme in Xcode, two simulators get launched, one for the iOS app and one for the WatchApp. I see the WatchApp starting but not the iOS app. If the iOS was previously running, it appears to be killed.
I put a break point on the application:didFinishLaunchingWithOptions: in the iOS app, method but this break point is never hit. Should it be.
I don't recall having these problems a couple of years ago when going through this.
Should running the WatchApp scheme automatically start the iOS app and allow it to be debugged? Should my didFinishLaunchingWithOptions: breakpoint get hit?
The other thing that is sort of strange and may be hint is that the External Displays list in the iOS simulator never shows watch app displays. I would think it should.
I've tried cleaning the project, restarting Xcode and even rebooting my computer. No joy.
No, the iOS and WatchApp have different targets, so running one from Xcode doesn't start the other one automatically.
You have to start one of them using Xcode in the usual way, then start the other app manually from its respective Simulator, than in Xcode use Debug>Attach to Process to see both apps in the debugger.
Ive submitted my first app and it has been approved. But I have a few issues that i'd like to ask what I should do about.
One of my images/icons that I have in my app showed correctly in my distributed binary at my end (running it in debug simulator from xcode) but on the app downloaded from the app store it is not showing at all?
IPads cannot see my app in their search of the app store?
IOS 4 is needed to run my app. How do i change it so that it can be run on IOS 3 aswell? And if i make it IOS 3 compatible does this mean that it cannot be run in the background at all (i.e. when the close out of my app and go back into it will it restart the entire app)
Also does anyone know whether submitting an update is quicker in the review process than submitting a entirely new app?
Thanks in advance for your help
Thats a QA issue. The simulator is just that and if you want to be sure that your App runs as you expect on hardware then you need to check it on hardware. There are instances of images that decode on simulator but not on hardware.
iPad only runs iOS 3.2 at the mo so if your app runs on 4.0 it wont show up for iPad.
See 2 and no you dont have multitasking in 3.2 so you need to make sure your app state persists across atomic launches. You'll need to remove/conditionally compile any 4.0 only API in your App. If thats a problem wait until November-ish.
Maybe, depends, probably no. Lead time on update/new submission is around 8 days +/- YMMV.