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

Testing and Deployment

Reply
New Member
Posts: 1
Registered: ‎08-08-2013
My Device: Developer
My Carrier: Developer
Accepted Solution

blackberry-deploy -installApp fails with error -104

Hey, I was wondering if someone could help me out with this.  

I've successfully created my debug token and I try to deploy with the following command

blackberry-deploy -installApp -device 169.254.0.5 -package <location of bar file> -password <password>

 

The output is:

Info: Sending request: Install
Info: Action: Install
Info: File size: 10275227
Info: Installing ...
Info: Processing 10275227 bytes
Info: Progress 0%...
Info: Progress 50%...
Info: Progress 50%...
Info: Progress 100%...
actual_dname::<package name>.testEJDtuDekSj.fZWEJZ1BCQZI
actual_id::testEJDtuDekSj-fZWEJZ1BCQZI
actual_version::1.0.408.0
result::failure -104

 

What does "result::failure -104" mean?
The only thing I can think of is that when I verify I have one sever warning but I don't think that should impact anything. The warning is 

[Android.apk]Smiley SadAndroidManifest.xml) native-code: x86:impact=5

 

Thanks

Trusted Contributor
Posts: 160
Registered: ‎11-17-2010
My Device: PlayBook, Z10, Q10

Re: blackberry-deploy -installApp fails with error -104

Hi,

 

Having native code in your Android application is not supported. The impact 5 warning shows that the apk2bar conversion was not succesfull, you should not be able to convert your application without removing the native code.

--
If you find this post useful please Like it.
If it solves your problem please mark as solution.
Highlighted
Trusted Contributor
Posts: 160
Registered: ‎11-17-2010
My Device: PlayBook, Z10, Q10

Re: blackberry-deploy -installApp fails with error -104

I see another potential problem in the log you've shared: if you are using a debug key, is the corresponding debug token installed to your device?

--
If you find this post useful please Like it.
If it solves your problem please mark as solution.