Native Development

[npross]

Using the Momentics IDE with the NDK is trying my patience.  I am debugging on a the playbook over USB not the simulator, my OS is Win7.

• 75% of the time when I launch my app to debug I get: Launching X has encountered a problem. Error in final Launch Sequence. Clicking on details I get a random assortment of failures like:

Error in final launch sequence
Cannot prepare and download the binary
unable to find result reply

• The time it takes to launch the app seems to take a random amount of time between 10s and 3 minutes the average is close to 1 minute.  The bar file is less than 1MB. 

Should I switch to the simulator? Does anyone else experience this or is it just me?  I have tried multiple computers and get the same results.

Any info on making the process more reliable and quicker would be really appreciated.

Thanks,

Norm

[npross]

The other common error is:

Error in final launch sequence
Cannot prepare and download the binary
Deployment Failed: Info: Sending request: Install and Launch
Info: Action: Install and Launch
Info: Debug native: on
Info: File size: 801130
Info: Installing ...
Info: Processing 801130 bytes

[BGmot]

Doesn't sound like common problem.

Try to capture traffic between your PC and PB with Wireshark, at least you will be able to rule out networking problems.

[MSohm · Accepted solution]

Please turn Wifi off on the PlayBook and let me know if you see any difference.

[npross]

Yes, turning off Wifi makes it much more reliable. Is this normal? Do I just have to turn off WIfi when I'm debugging via USB?

I do get a strange error still.  But it seems to be ignorable:

An internal error has occurred.
java.util.concurrent.RejectedExecutionException

[MSohm]

It could be a routing issue if it's trying to connection over WiFi instead of USB.  Do you have any firewall software enabled on your computer or VPN connection?

Try the following:

• Right click on your PlayBook target in Project Explorer
• Click on Properties
• Click on BlackBerry Tablet OS

What do you see listed as the IP address?  Is it the USB address (likely 169.254.0.1) or your WiFi address?  If it is the WiFi address replace it with the USB address.

[npross]

No it's definitely the USB target (169.254.0.1).  I deleted the wifi target long ago.  I briefly tried debugging via wifi and it was extremely slow.  I have turned off all firewalls no change, I do use a VPN to connect to work but it is off (and nothing would work if the VPN was on, it reroutes everything).

I have a workaround, thanks very much for the quick response.

Someday when I have more time, I'll try installing on a clean machine and see if the problem goes away.

Norm

[punto]

What happens if we're debugging an app with network functionality? Can the device get network through the USB connection?

[MSohm]

---

punto wrote:

What happens if we're debugging an app with network functionality? Can the device get network through the USB connection?

---

No, you would need to have WiFi connected.

[npross]

Well, I thought it was better but today it is just as bad as ever.  

I have disabled every network adapter on my laptop so there is only one adapter -- the Research In Motion Network Device USB adapter.  I have disabled wifi on the playbook too.  I still get less than 50% success starting a debugging session.  

Error in final launch sequence
Cannot prepare and download the binary
Deployment Failed: Info: Sending request: Install and Launch
Info: Action: Install and Launch
Info: Debug native: on
Info: File size: 601622
Info: Installing com.example.pbChart.testDev_ple_pbChartcad4161b...
Info: Processing 601622 bytes

Even when it succeeds i get: 

An internal error has occurred.
java.util.concurrent.RejectedExecutionException

I tried using wireshark but it doesn't seem to like the Research In Motion Network Device.  

Any other suggestions? 

Thanks,

Norm