Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raccoon don't see/can't download apps that are in development mode #91

Open
thecoderok opened this issue Mar 30, 2021 · 3 comments
Open

Comments

@thecoderok
Copy link

Sample app: https://play.google.com/store/apps/details?id=com.coldfiregames.dungeon.manager.tycoon.idle.game&hl=en&gl=US

"This app is in development. It may be unstable."

image

Tested in v. 4.17.0
Exception thrown: "com.akdeniz.googleplaycrawler.GooglePlayException: The item you were attempting to purchase could not be found."

image

I can download this app on the phone

@jpstotz
Copy link
Contributor

jpstotz commented Mar 31, 2021

I don't think that the development state is the main problem that you can not download the app.
I would assume the reason is the used device profile you use for downloading. The device profile used by Raccoon is pretty old if I remember correctly and most likely misses at least one feature that is required by this game (the game seems to require OpenGL and a 64bit device).

@thecoderok
Copy link
Author

I believe that the error is different when device is not compatible.

com.akdeniz.googleplaycrawler.GooglePlayException: Your device is not compatible with this item.

@jpstotz
Copy link
Contributor

jpstotz commented Apr 1, 2021

You are correct, usually you can query at least the app meta data even using an incompatible device. But for an unknown reason in a few cases Google sends back an "not found" result if you are trying to query the app meta data but it definitely depends on the used account respectively the used device profile, because using a different account and device profile I can successfully get the app meta data and also download the apk.

I have not figured out why it works for some devices and fails for others. As Google very often update the protobuf based API and add or removes features it is very difficult to identify the reason behind this behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants