Replying to me isn't going to get development moving. And after nearly five years since I last used the extension, I don't believe anything will. Of course, you could check for the source code on GitHub yourself and start maintaining things. You clearly have the desire to do the work.
Sorry, I wasn't demanding further maintenance of the project, just thought I'd spark some interest in whoever might want to tinker with it.
Once you get used to downloading apps in the comfort of a desktop, it's hard to go back to a mobile device downloading and backing up each one at a time.
Definitely one of my favorite extensions yet, guess will just have to dig into the code.
The authentication fix in the latest version 2.1.10 was the simple deletion of these lines of code.
I'll try to add it back on and see what happens.
/*** REMOVE ***/
, marketDA;
if ((marketDA = /MarketDA..(\d+)/.exec(data))) {
marketDA = marketDA[1];
BrowserCookie.set({
url: appUrl,
name: 'MarketDA',
value: marketDA
}, function() {
BrowserCookie.set({
url: redirectUrl,
name: 'MarketDA',
value: marketDA
}, function() {
});
});
}
As probably everyone has noticed by now, pretty much all APK downloaders have been started to fail lately.
The reason for this is a recent change in Google Play's login mechanism, using session cookies rather than tokens.
One interesting thing to note is that in FDFE urls, the following two url parameters are supported:
ipCountryOverride
mccmncOverride
Which when implemented correctly would allow to bypass Google Play's region/carrier locks without using messy proxys.