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
Contributor
jansensan
Posts: 30
Registered: ‎04-04-2012
My Device: BlackBerry Playbook
My Carrier: Telus
Accepted Solution

FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

It's been a while since I played with AIR and the Dev Alpha. I got the latest SDK (3.1.1), my Dev Alpha says it has the latest software release (10.9.10.35).

 

However, a simple hello world doesn't work, I get something like that: 

 

Using Flex SDK 4.5 Debugger Adapter.

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 72000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 64000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 56000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 48000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 40000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 32000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 24000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 16000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, will try to connect for the next 8000 ms

[Info] Listening to port 7935.

[Info] Could not connect to the player, debug session stopped. Maybe you do not have the Debug Flash Player installed.

 

Now, if I simply try on the desktop rather than on the machine, it works fine. So what's up? What should I look for?

--
mat janson blanchet
twitter: @jansensan, portfolio: http://jansensan.net/portfolio, tech blog: http://jansensan.net
Please use plain text.
BlackBerry Development Advisor (Retired)
dmalik
Posts: 427
Registered: ‎02-22-2012
My Device: BlackBerry Z10, BlackBerry Dev Alpha C, BlackBerry PlayBook
My Carrier: Bell

Re: FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

Hi Mat,

 

Some things to look for:

 

- Developer mode is on

- Debug tokens have been uploaded to the device

 

Regards,
Dustin

Follow me on Twitter: @dustinmalik
-----------------------------------------------------------------------------------------------------
Keep up to date on BlackBerry development: http://devblog.blackberry.com/
Please use plain text.
Contributor
jansensan
Posts: 30
Registered: ‎04-04-2012
My Device: BlackBerry Playbook
My Carrier: Telus

Re: FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

Yup, my device is has dev mode activated. I also have the Flash Player Debugger installed.

 

bb10-dev-mode-on.png

--
mat janson blanchet
twitter: @jansensan, portfolio: http://jansensan.net/portfolio, tech blog: http://jansensan.net
Please use plain text.
BlackBerry Development Advisor (Retired)
dmalik
Posts: 427
Registered: ‎02-22-2012
My Device: BlackBerry Z10, BlackBerry Dev Alpha C, BlackBerry PlayBook
My Carrier: Bell

Re: FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

Do you have your Author and AuthorID tags filled out in your bar-descriptor.xml file? For example here are mine:

 

<!--  Name of author which is used for signing. 
         Must match the developer name of your development certificate -->
    <author>Dustin Malik</author>
   <!--  Unique author ID assigned by signing authority. Required if using debug tokens -->
    <authorId>gYAAgN-md4mGQMOzFWviE8rdVM</authorId>

 authorId can be found in your debugToken.bar archive in the MANIFEST.MF file. Default location on Windows 7 is - C:\Users\USERNAME\AppData\Local\Research In Motion

Follow me on Twitter: @dustinmalik
-----------------------------------------------------------------------------------------------------
Keep up to date on BlackBerry development: http://devblog.blackberry.com/
Please use plain text.
Contributor
jansensan
Posts: 30
Registered: ‎04-04-2012
My Device: BlackBerry Playbook
My Carrier: Telus

Re: FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

Hmm you are right, there is nothing there... I thought FDT was handling this? I have never had issues with publishing to the Dev Alpha before. My bar-descriptor.xml is really all commented out...

 

I'm on a Mac, where should I look for what you suggest?

 

bar-descriptor.png

--
mat janson blanchet
twitter: @jansensan, portfolio: http://jansensan.net/portfolio, tech blog: http://jansensan.net
Please use plain text.
BlackBerry Development Advisor (Retired)
dmalik
Posts: 427
Registered: ‎02-22-2012
My Device: BlackBerry Z10, BlackBerry Dev Alpha C, BlackBerry PlayBook
My Carrier: Bell

Re: FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

[ Edited ]

Flash Builder 4.7 does but I don't have much experience with FDT to know if it did before or not.

 

Anyway here is a full rundown from our documentation: https://developer.blackberry.com/air/documentation/bb10/update_bar_descriptor_cfg_fdt.html 

 

Follow me on Twitter: @dustinmalik
-----------------------------------------------------------------------------------------------------
Keep up to date on BlackBerry development: http://devblog.blackberry.com/
Please use plain text.
Contributor
jansensan
Posts: 30
Registered: ‎04-04-2012
My Device: BlackBerry Playbook
My Carrier: Telus

Re: FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

I just saw this article: Blackberry 10 Gets AIR 3.5 Upgrade

 

Could it then be that it was because I merged the BB10 SDK 3.1.1 with the AIR 3.6 SDK? Where could I find an always updated page where it says what is the max AIR SDK that can be merged with the BB10's?

--
mat janson blanchet
twitter: @jansensan, portfolio: http://jansensan.net/portfolio, tech blog: http://jansensan.net
Please use plain text.
BlackBerry Development Advisor (Retired)
dmalik
Posts: 427
Registered: ‎02-22-2012
My Device: BlackBerry Z10, BlackBerry Dev Alpha C, BlackBerry PlayBook
My Carrier: Bell

Re: FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

You are able to use the 3.6 SDK but you have to deploy to AIR 3.1. Here is some documentation on how to do so - https://developer.blackberry.com/air/documentation/bb10/change_runtime_fdt.html

 

Regards,
Dustin

Follow me on Twitter: @dustinmalik
-----------------------------------------------------------------------------------------------------
Keep up to date on BlackBerry development: http://devblog.blackberry.com/
Please use plain text.
Contributor
jansensan
Posts: 30
Registered: ‎04-04-2012
My Device: BlackBerry Playbook
My Carrier: Telus

Re: FDT5 → Dev Alpha: "Could not connect to the player, debug session stopped"

It turns out that the BB10 SDK was merged with higher than 3.1, which is why I had an issue. Too bad I didn't get a sensical error message...

 

Any news on when AIR SDK 3.5 will be available for BB10?

--
mat janson blanchet
twitter: @jansensan, portfolio: http://jansensan.net/portfolio, tech blog: http://jansensan.net
Please use plain text.