I get quite a bit of spam mail offering me to boost the download count of my own apps on Play (thanks Google for requiring me to maintain a
spam support address). I also get occasionally asked if my APK downloader can be used to increase an app’s download counter. The short answer is: you can’t use Raccoon to cheat on Play. Period. Read more ›
I should probably mention this, even though it’s not actually worth mentioning: Raccoon v4.1.6 reverts to the Raccoon v3.x policy for storing credentials. That is, your password will be stored on disk again.
Read more ›
Just learned something new today that feels like I should have known it for years (probably even did once, but then forgot): did you ever have the “page 99” problem? You know exactly what app you want, how the name is spelled, what the icon looks like, but now matter what you type into the search field, the app in question is always buried on page 99 (or later) in the search results. The answer to this problem, of course, is not to search for the app, but locate it by package name. On the Play website that means fiddling around with URL parameters, in Raccoon, you’d (currently) have to go through the commandline. Neither is particularly user friendly. Read more ›
Looks like I spoke to soon in yesterday’s post, announcing that Raccoon v4.1.3 would solve the “Error on download issue”. It does, kinda, but it’s not a final solution, as it requires an annoying workaround (see below). Read more ›
Just a quick heads up. Raccoon v4.1.3 should fix the “app not downloading” issue that has arisen yesterday. However, I’m currently in a rush and don’t have time for a proper, tested release.
PS: If you haven’t done so already, now would be a really good time to buy a premium key. Your money is what keeps the project alive.
Well folks, we need to talk. Today, I opened my mail client and was greeted with a “Raccoon is broken, fix it!” message. Most of the time that’s the result of a handling error, but once in a while, usually twice a year, Google actually changes something, causing Raccoon to stop working. Figuring out what what that something is, can easily take several days of research. Read more ›
I had this discussion with a friend the other day, who is now the proud owner of a fingerprint protected front door and smartphone, but since fingerprint scanners are creeping into more and more security appliances, it is worth repeating it here. Read more ›
People ask (me) fairly often, how Raccoon handles their Google account (and if it’s safe to trust the software with their passwords). From my point of view, that’s a funny question. I’m always tempted to answer: “if the idea of loosing your account sounds scary to you, then maybe you already trusted Google too much!”. But that’s a discussion for another day. Read more ›
The question came up in a support request, but is probably interesting enough to blog about: “How do I write a script to copy apps from Raccoon‘s own repository to some place else?” Read more ›
The plan was to rewrite DummyDroid from scratch, get rid of the ugly code and make it more userfriendly (ideally let it clone a device via USB) while I’m at it. Unfortunately, that would have taken several weeks (yes, the code rot is that bad) and in the meantime, no one would have been able to generate GSF IDs for mock devices (there are/were alternatives to DummyDroid, but I don’t think their respective authors bothered adapting to Google’s changed login procedure, yet). So, hack job time!
DummyDroid v1.2 is a case of “it compiles, ship it”. Cobbled together by merging in some code from Raccoon, compiled by guessing how the build process was suppose to work, using a source tree that’s in disarray. I’m not proud of it. I probably won’t bother cleaning things up, so no source code at the moment, either. This is only a temporary solution anyways.