Well, that went faster than expected. Thanks to all who helped! The trick simply was to masquerade as a Jelly Bean device when requesting the AUTH token (cheers for legacy devices which Google can’t afford to lock out of Play, yet). While I was at it, I also bumped the specs for the fake device, Raccoon creates if you don’t provide a GSF id of your own. This should solve most “App not found” errors.
Of course, it’s kinda weird that Raccoon logs into Play as a Jelly Bean and then suddenly becomes a Marshmallow, but it seems to work just fine for now.
As for DummyDroid: no ETA. I shouldn’t even have spent the evening on Raccoon. But with Raccoon now mimicking a more recent device, there shouldn’t be a pressing need for it.
