03-23-2013 02:25 PM
I have an issue with the signing requirement to bump the app version. Most of the time, the .bar files I sign come from Android apks ... of free Android apps I obtain via an Android tablet. In other words, I cannot change their version.
I'm trying to reconvert an apk I had already tried once, and deleted by mistake. Sure enough barsigner won't let me sign it telling me the file has been signed previously ...
Is there really no way around this? I've looked around on my workstation to find a database of signed files, but apparently this information is stored somewhere online ... so that also means that if I convert an apk for my OWN use, this blocks everyone else from doing the same?!
Is there a way to 'hack' an apk to change its name and/or version, without having access to the original code?
03-23-2013 02:47 PM
03-23-2013 03:00 PM
converting, not porting. It's just a matter of repackaging - if BB had set things up so that regular apk files worked it wouldn't even be necessary. As a matter of fact, the apk I'm trying to convert is a game from a big company - a so-called fremium model where the software itself is free but one pays for certain features. I cannot help but think that I'd be doing them a favour if it turns out the game runs better on the PB than on my buggy Android tablet.
[rant]I cannot begin to see what's more wrong with converting a free application than with side-loading it on a regular Android device. Apart from the fact that if I sign the .bar no one else can sign the same version ... but frankly, that's not a decision I made.
There used to be a time when one had full powers to decide what to run on one's computing hardware, be it precompiled or programmed one-self. I still think that should be possible, no matter how conforting it is to know it's not overly easy to mess things up completely.