10-26-2011 12:05 PM
I just submitted and had approved a new version of my app, however, my users are getting a secure api error when trying to run the app. This is very odd for multiple reasons:
1) I've quadruple checked the build I uploaded was signed -- I installed it on a phone manually and it works fine, however, when downloaded from app world it does not.
2) Shouldn't the COD uploader check to see if the app is signed prior to submission?
3) Shouldn't the reviewer see this issue?
I've sent an email but have yet to receive a response -- this is very frustrating.
10-26-2011 02:07 PM
I recall similar issue discussion in the past. The reason was that some carriers my cut the signing off the cod file.
Let me explain in details - when you first generate the cod and jad file, the jad file contains the cod file length. After signing few more bytes are added to the cod file, but the jad file length remains the same. And in some rare situation the carrier proxy/firewall or whatever server may decide to cut the cod file length based on the jad file value, thus cutting the signing.
However this should not happen for apps in BB App World, as the jad file is generated by BB App World based on the uploaded cod file.
10-26-2011 02:24 PM
10-26-2011 02:52 PM
Well, the app was actually originally written pretty terribly -- one binary for each resolution of device, so there were three binaries uploaded. It's every user who's trying to use one of those specific binaries, the other two binaries are working fine. I've made sure the binary that is affected was in fact signed, and it was, so I'm not sure why that one has an issue.
This release was to address a lot of low hanging fruit, where now I'm working condensing down to one build which will work on all resolutions with minimal tweaks.
10-26-2011 03:58 PM