Apps Crash the iPad
We have 5 apps that are all made with AIR and Flex. Sometimes, when opening an app (no specific one), the iPad freezes and we need to hard reset it by holding the Home and Power buttons for a couple of seconds. It happens mainly on the iPad 1 (60-75%). The problem can be reproduced easily on the iPad 1 when successively opening 2-3 apps.
Trying to nail down the problem, we added the default iOS splash screen image and Flex's splash screen image to see how goes the loading process.
For the iOS default splash screen image, we added the 'Default-Landscape.png' and 'Default-LandscapeRight.png' images in the root application directory as specified here: http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac1e63e3d129907d2886-8000.html#WS901d38e593cd1bac58d08f9112e26606ea8-8000.
For the Flex splash screen image, we specified the 'splashScreenImage' property on the application:
splashScreenImage="@Embed('/../resources/embed/SplashScreen.png')".
iOS image is marked with number '1' and Flex image is marked with number '2'.
We noticed that when the iPad freezes, it always shows the image marked with '1'.
We don't really know what is happening after that point but it seems that Flex is trying to load but never actually loads since the image marked with '2' doesn't show up.
First, I was thinking about memory utilization, but it happens on iPad 2 with no apps open.
It doesn't seem to be related to a specific app since it happens to all of them.
We tried to reproduce with an empty AS3 only mobile application, but with no results.
We tried to reproduce without the native extensions, but with no results.
We continue our investigation with emphasis on memory utilization but we have no clue at this time.
Most specifically, we'll begin with:
- we will profile the memory utilization (maybe we're hitting the max, specifically on the iPad 1)
- we will move the code from the 'preinitialize' event handler to the 'applicationComplete' event handler (maybe it takes to much processing power and memory at the 'preinitialize' stage)
- we'll try to reproduce with an empty Flex mobile application
Questions:
- Did you ever see this loading problem on other apps made with AIR and Flex?
- Would you have any clue about what could go wrong in the loading process?
- Would you have some specific recommendations on what to do or not do in apps made with AIR and Flex?
- Would you have suggestions where to put the first executed code (preinitialize, initialize, applicationComplete)?
More infos on our apps
- Compiled in GPU mode
- Packaged in AdHoc mode with the distribution certificate and AdHoc provisioning profile.
- Flex 4.6.0.23201
- AIR 3.1.0.4880 (AIR 3.2 is worst)
- Using native extensions
AdChoices