09-20-2013 12:46 PM
We are having difficulties getting a signed bar file to load and run correctly on a Q10 device.
We have packaged the application with 10.1 and signed it with 10.2 command line signer using the download bbidtoken.csk and author.p12.
The signing command reports that it has signed the bar file.
When we try to install the app you see the app icon on the home screen but when you try to run it from the icon it brings up a black window that fills the screen for a few seconds then closes.
Any thoughts on what could be wrong?
09-20-2013 03:55 PM
09-23-2013 04:21 AM
09-23-2013 04:50 AM
Yes we have tested on the device directly from eclipse using the debug token (no portals) and it works correctly. We use Jenkins to build, package and sign the app on a separate build machine using the command line (built with 10.1, signed with 10.2). The signed bar file installs on the Q10 device but the app behaves as described.
09-23-2013 10:54 AM
09-23-2013 11:00 AM
No I am not modfiying the .bar file. If I install the author.p12 from Jenkins to my personal certifcates store and then view the cert I see "The integrity of this certificate cannot be guaranteed. The certificate my be corrupted or may have been altered." Whereas if I take do the same with the p12 from my machine I only get "windows does not have enough information to verify this certificate" because it doesn't have the full cert chain. Seems the .p12 cert may have an invalid digital signature.
09-23-2013 11:11 AM
This is a duplicate thread there's more in this one...