0ca0f65f75
Fix to include device.properties on build |
||
---|---|---|
gpapi | ||
scripts | ||
test | ||
.gitignore | ||
.travis.yml | ||
googleplay.proto | ||
LICENSE.md | ||
MANIFEST.in | ||
README.md | ||
setup.cfg | ||
setup.py |
Google play python API
This project contains an unofficial API for google play interactions. The code mainly comes from GooglePlayAPI project which is not maintained anymore. The code was updated with some important changes:
- ac2dm authentication with checkin and device info upload
- updated search and download calls
- select the device you want to fake from a list of pre-defined values (check
device.properties
) (defaults to a OnePlus One)
Build
This is the recommended way to build the package, since setuptools will take care of
generating the googleplay_pb2.py
file needed by the library (check the setup.py
)
$ python setup.py build
Usage
Check scripts in test
directory for more examples on how to use this API.
from gpapi.googleplay import GooglePlayAPI
mail = "mymail@google.com"
passwd = "mypasswd"
api = GooglePlayAPI(locale="en_US", timezone="UTC", device_codename="hero2lte")
api.login(email=mail, password=passwd)
result = server.search("firefox")
for doc in result:
print("doc: {}".format(doc["docid"]))
for cluster in doc["child"]:
print("\tcluster: {}".format(cluster["docid"]))
for app in cluster["child"]:
print("\t\tapp: {}".format(app["docid"]))
For first time logins, you should only provide email and password. The module will take care of initalizing the api, upload device information to the google account you supplied, and retrieving a Google Service Framework ID (which, from now on, will be the android ID of your fake device).
For the next logins you should save the gsfId and the authSubToken, and provide them as parameters to the login function. If you login again with email and password, this is the equivalent of re-initalizing your android device with a google account, invalidating previous gsfId and authSubToken.