Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Adobe AIR Development

Reply
Super Contributor
Posts: 440
Registered: ‎01-13-2011
My Device: Playbook
My Carrier: NA

App opens then closes?

I'm using Air 3.1, I;ve downloaded the sdk from here:

 

http://www.adobe.com/devnet/flex/flex-sdk-download.html

 

I'm using FB 4.6 on OSX 10.8.

 

My PlayBook is running 2.1.0.1526.

 

All debug tokens are correct and valid and in date.

 

When I run my app or debug it via usb, it opens on the Playbook for a flash (I can see the splashscreen for a second) then shuts down.

 

I was just wondering if anyone could let me know where I'm going wrong.

 

 

--------------------------------------------------------------------------------------------------
BlackBerry Apps: Instruments | ARTPAD | Piano | Drums | Xylophone
Retired
Posts: 427
Registered: ‎02-22-2012
My Device: BlackBerry Z10, BlackBerry Dev Alpha C, BlackBerry PlayBook
My Carrier: Bell

Re: App opens then closes?

I assume you have the BlackBerry PlayBook SDK for AIR installed - https://developer.blackberry.com/air/download/#playbook

 

Have you tried just creating a blank project and trying to get that running? Flash Builder 4.6 should have AIR 3.1 installed on it by default. Does you app.xml point to AIR 3.1?

 

<application xmlns="http://ns.adobe.com/air/application/3.1">

 

Regards,
Dustin

Follow me on Twitter: @dustinmalik
-----------------------------------------------------------------------------------------------------
Keep up to date on BlackBerry development: http://devblog.blackberry.com/
Super Contributor
Posts: 440
Registered: ‎01-13-2011
My Device: Playbook
My Carrier: NA

Re: App opens then closes?

Yes I have installed the PlayBook Air SDK..

 

My xml also points to 3.1

 

I did create a new project that just drew a square on screen - this worked ok.

 

So I'm not sure what the problem is. I've imported my old release code for an app. This worked but now it doesnt with the new PlayBook Air SDK.

 

Can anyone help?

 

 

--------------------------------------------------------------------------------------------------
BlackBerry Apps: Instruments | ARTPAD | Piano | Drums | Xylophone
Contributor
Posts: 15
Registered: ‎08-05-2013
My Device: Simulator
My Carrier: Telekom

Re: App opens then closes?

[ Edited ]

Same problem here, I downloaded all the latest SDK and simulator just a couple of days ago and I can not make the simplest example launch (I also draw a square on screen Smiley Very Happy)

 

Splash screen pops up, app immediately closes. I was unable to access the logfiles so far. Using blackberry-deploy xxx -getFile logs/air-trace myapp.log results in "access denied" on air-trace.

 

For the record I am using command line tools.

Contributor
Posts: 15
Registered: ‎08-05-2013
My Device: Simulator
My Carrier: Telekom

Re: App opens then closes?

Alright so for me the problem was that I was compiling the swf to the subdirectory "bin" and then referencing that from in the command line. Putting it to the root directory from which the command line is called, it works.

 

Duh

Highlighted
Retired
Posts: 427
Registered: ‎02-22-2012
My Device: BlackBerry Z10, BlackBerry Dev Alpha C, BlackBerry PlayBook
My Carrier: Bell

Re: App opens then closes?


JeffLemon wrote:

Yes I have installed the PlayBook Air SDK..

 

My xml also points to 3.1

 

I did create a new project that just drew a square on screen - this worked ok.

 

So I'm not sure what the problem is. I've imported my old release code for an app. This worked but now it doesnt with the new PlayBook Air SDK.

 

Can anyone help?

 

 


In the past this has happened to me when I forgot to update the references to the ANE files. Make sure in your project settings that everything is pointing to the same BlackBerry AIR SDK.

Follow me on Twitter: @dustinmalik
-----------------------------------------------------------------------------------------------------
Keep up to date on BlackBerry development: http://devblog.blackberry.com/
New Developer
Posts: 31
Registered: ‎04-21-2011
My Device: Playbook
My Carrier: N/A

Re: App opens then closes?

I'm experiencing the same thing. I have followed all of the instructions here:

 

https://developer.blackberry.com/playbook/air/documentation/ww_air_getting_started/Create_your_first...

 

The app signs and installs successfully, but when it executes it just flashes the screen and closes.

 

rtholmes@craigleith:~/Dropbox/Public/sandbox/airTest$ ./bundle.sh 
Warning: Using default icon: /Applications/dev/BlackberryAirSDK_2.1/blackberry-tablet-sdk-2.1.0/bin/../samples/icons/blackberry-tablet-default-icon.png
Info: Package created: AIRHelloWorld.bar
Info: Bar signed.
Info: Sending request: Install and Launch
Info: Action: Install and Launch
Info: File size: 266162
Info: Installing net.example.test.gYABgL5oRdldnaOr6p_SeG-A_Dg...
Info: Processing 266162 bytes
Info: Progress 100%...
Info: Progress 100%...
actual_dname::net.example.test.gYABgL5oRdldnaOr6p_SeG.A_Dg
actual_id::gYABgL5oRdldnaOr6p_SeG-A_Dg
actual_version::1.0.0.1
result::success
Info: Launching net.example.test.gYABgL5oRdldnaOr6p_SeG.A_Dg...
result::11178132
Info: done

 

Any tips would be _greatly_ appreciated (I'm also on OS X,

blackberry-tablet-sdk-2.1.0, AIRSDK_Compiler_3.9).

.

Developer
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10
My Carrier: Verizon

Re: App opens then closes?

You're using AIR 3.9? That is not compatible with BB SDK 2.1. Only 3.1 AIR for 2.1 works. AIR 3.5 for BB 10.2.
New Developer
Posts: 31
Registered: ‎04-21-2011
My Device: Playbook
My Carrier: N/A

Re: App opens then closes?

Sorry, I was using "-forceAirVersion 3.1". I installed the Air 3.1 SDK and reinstalled the tablet SDK but the result remains the same.
Developer
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10
My Carrier: Verizon

Re: App opens then closes?

Is this on the device or the simulator? Have you tried both?
If device, have you restarted the device?
Are you getting any kind of debug stack trace?