04-18-2012 03:13 AM
Isn't the captive runtime feature suppose solve the problem of OSes not being updated with the latest AIR SDK?
I have tried to compile and package a project using FB 4.6, Playbook SDK 2.0 and Flex SDK 4.6 with an AIR SDK 3.2 (overlay) with captive runtime. However, a second after the splashscreen, the app disappears out of memory.
The same procedure works fine on my HTC Desire (Android 2.3.5).
Maybe I'm simply missing a required setting?
04-18-2012 06:30 AM
04-18-2012 07:45 AM
04-18-2012 08:10 AM
"You do not need Captive Runtime for the PlayBook. AIR runtime is already installed. It is only available for iOS and Windows OSs."
Yes you do! I need to get an app based on AIR SDK 3.2 running on the Playbook. Reason being, that AIR SDK 3.1 has a huge number of rendering issues resolved in 3.2. The AIR runtime is also available on Android, but not necessarily 3.2, hence the captive runtime option for iOS, Windows and Android.
"And it does not make any sense to have an AIR app to Android to PlayBook."
Not sure what you are saying here. It definitely doesn't reflect what I said.
04-18-2012 08:52 AM
04-18-2012 09:07 AM
04-18-2012 09:52 AM
A bit of background...
The AIR runtimes for Android, IOS, Windows & Mac are maintained by Adobe, and are packaged with the AIR SDK distributions.
The runtime for PlayBook is maintained by RIM, not by Adobe, and is part of the OS installation. We'll have to wait for RIM to update to 3.2.
04-18-2012 12:14 PM
Probably upgrading to AIR 3.2 will break a lot of current apps develop by RIM for the Playbook. So it will be 2 huge efforts. For sure they know all the advantages of commiting to these 2 efforts but they are in a bad situation right now - have you seen the last quarter financial reports ? - so probably is better keep their money and minds on the next big thing: BB10 (Cascades Qt)
What would guys prefer, BB10 or AIR 3.2?
04-18-2012 01:19 PM
04-18-2012 01:50 PM
Supporting the AIR captive runtime is exactly what would avoid these problems. The application doesn't depend on the environment it runs on nor will it make a device owner break existing applications by forcing an OS or SDK upgrade.