Gnarg! I had android.clients.google.com hardcoded in my 📁 /etc/hosts file the whole time! No idea why. Best case scenario: it didn’t matter at all. Worst case scenario: it raised alerts on my test accounts and/or IP address. Stupid problem: no way of finding out which.
This calls half of last weeks work into question.
In other news: I got an email about a CAPTCHA affected Raccoon instance recovering automatically. Appears as if you can sit this out. Not that you’d want to or that this is practible a solution.
Time for a progress report:
Some of you might have found yourself being asked to solve a captcha when adding a new profile, with Raccoon providing no means to show the image nor accepting an answer.
Ok, just wanted to add a nice feature for the custom ROM community: automatically build an 📁 update.zip from tagged apps in a Raccoon repository. It looked easy, but of course:
Thanks again, Google…
Now, that was a waste of time! Tried to rewrite Raccoon’s protocol buffer definitions from proto2 to proto3. Turns out that in their infinite wisdom, Google retired the
required keywords. As a result, hazzer functions are no longer supported. In other words, it is impossible to tell the difference between a field that has not been set and a field that has been set to its default value. Needless to say that the DFE API (“Google Play”) makes heavy use messages with unset fields.
Why Google? Why?!
I have this love/hate relationship with semantic versioning. It’s great for libraries, but not so great for apps as it tends to confuse users. The really annoying thing, though, is the rattail of pre release and meta tags that may be appended and the insanely complex rules that must be followed when you do.[…]
The Finsky useragent (not the same as the Chrome useragent) is used to determine app/device compatibility.
Let's dive deep into the Android OS and talk a bit about how app compatibility is determined and how big G keeps track of your device.