We have a ionic cordova app built for ios and the application is some what big. And the app is working fine but sometimes in iPad 4 or other devices the application crashes saying memory warning in xcode. And we are using a timeline view similar to facebook app's newsfeed. And it contains images in each item. And this is a infinite scroll list and the list can grow very big. Currently we are using ng-repeat to populate list but we tried migrating it to collection-repeat, and the crash frequency is decreased but its still crashing. If i could find any blogs or links which will guide me through the performance tuning tips in ionic application it would be helpful.
I simply rebooted the simulator by going to Hardware > Reboot. That fixed my app-crashing issue. Good luck with your app!
Related
I created a couple of apps and side loaded them on my iPhone.
I was playing around with my iPhone screen recorder and noticed the apps I side loaded, would close out.
Apps like LinkedIn, Twitter, shopping apps will stay on top.
Is there a setting in Xcode that prevents this?
I believe I found the answer. I had updated to iOS 11.0.1, thats when the crash started. Worked well with iOS 11. Just reloaded the app from Xcode and it works now. At this writing, the Apple Developer website is down for maintenance, so I am unable to load my other apps.
I'm running the official React Native 0.22.2 "Movies" example on a physical iPad Mini 2.1 running iOS version 9.3.1, not on the simulator.
I selected the Release scheme and added main.jsbundle to run without a server.
When I scroll down the list of movies and it stops, I click on the movie row. However it takes a second or two to finally respond and open the details page.
Is there some flag or setting I'm missing to get fast performance?
If not, this is a big disappointment. Everything I read suggested it would be as responsive as a native app.
Also just ran on iPad mini running 9.2. It has the same lag when trying to click on a movie row.
Here's a video demonstrating the issue:
https://www.youtube.com/watch?v=2D6gMMVbF6k
I want to know if it's a mistake to start a project with React Native. If the performance is this bad, I'll just stick with Swift.
I have an app which has started freezing at random when I run it on the iPad. It does not happen on any iPhone, not yet anyway. I download a bunch of images on my app, to display on a list, and store them to the internal cache in the background. Also, the app uses modal segues. The freeze is so random I am not able to pinpoint the source of the problem.
All this has started after the device was upgraded to iOS 7. I have also upgraded my Xcode to version 5 and am using iOS SDK 7. Everything was working fine on iOS 6.
Has anyone been facing similar problems?
Good evening,
My app is a simple calculator that starts with a main menu. It is working as designed on my iPad2, but a friend who downloaded it in the App Store is unable to even launch to the main menu on his iPad1.
There seem to be no memory issues, according to Instruments.
I set the deployment target in the summary screen to iOS 5.0. Is there anything else I need to do to get this to work on iPad1?
I're released an iPad game which is developed on the Cocos2d framework. Ive tested the game on a number of devices iPad 3, and iPad 2 and never had any issues.
Now i'm getting a few reports back that its not launching properly on some devices. People are saying they are seeing the default.png images then the app is closing.
Any ideas?
Without crash report this is just a guessing game.
By all means try to reproduce the problem on your side.
Possible problems:
1. If the app takes too long to launch it will be closed by iOS.
2. If it does not have enough memory it will not launch as well.
Try the following:
I. Open many other heavy apps in the background so there is not much memory.
See how it affects your app launch.
II. During launch try to use as many fast taps as possible and fast gestures.
There is possibility that very early taps are not serviced properly or at all
and that can cause the crash.
III. Test on many devices as you can - especially low end.
I found the issue, it was to do with the social framework running on older devices where it isn't available.