Fix download of purchased apps #116
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This updates delivery() to use the newer protobuf definition in the same way that download() was updated in 46b4271.
Open
matt668
added a commit
to matt668/googleplay-api
that referenced
this pull request
Jan 9, 2024
Merge pull request NoMore201#116 from gurnec/fix-purchased-downloads
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates delivery() to use the newer protobuf definition in the same way that download() was updated in 46b4271.
Prior to this update, delivery() would fail to retrieve the versionCode, and set it to None. The download URL would then include
vc=None. It seems that Google was OK with this in the past, delivering the latest version of the app, but currently they return an HTTP "400 Bad Request" error along with the message "Error retrieving information from server. DF-DFERH-01". This update fixes things for me.(This might be related to #113, though the traceback doesn't match up right....)