Add support for Google auth token as alternative to aas-token#232
Open
benedikt90 wants to merge 1 commit intoEFForg:masterfrom
Open
Add support for Google auth token as alternative to aas-token#232benedikt90 wants to merge 1 commit intoEFForg:masterfrom
benedikt90 wants to merge 1 commit intoEFForg:masterfrom
Conversation
This file contains hidden or 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
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.
Full disclosure: This change was done with an LLM and requires: EFForg/rs-google-play#26
Summary
This PR adds support for AUTH tokens (e.g., from Aurora Store's token dispenser), allowing users to authenticate without going through the OAuth → AAS token flow.
Motivation
Aurora Store's token dispenser provides AUTH tokens (starting with
ya29.) for anonymous access to Google Play. Previously, apkeep only supported AAS tokens, making it incompatible with these dispensers. This PR bridges that gap.Changes
New CLI Option
--auth-token <TOKEN>: Accepts an AUTH token directly (mutually exclusive with-t/--aas-token)Modified Files
src/cli.rsgoogle_auth_tokenargument with--auth-tokenflag--aas-tokensrc/main.rsaas_tokenandauth_tokenfrom CLI and config fileya29.are treated as AUTH)accept_toswas reading from wrong CLI argument (list_versionsinstead ofgoogle_accept_tos)src/download_sources/google_play.rsdownload_apps()signature to accept both token types asOption<&str>login()call afteraccept_tos())USAGE-google-play.mdauth_tokenoptionConfig File Support
Users can now specify
auth_tokenin their config file:Usage Example
Bug Fixes
--accept-tosflag not working: The flag was reading from the wrong CLI argument (list_versionsinstead ofgoogle_accept_tos)Dependencies
This PR requires the corresponding changes to the
gpapicrate that addset_auth_token()support.Before submitting this PR:
EFForg/rs-google-playCargo.tomlto use the new gpapi version:Backward Compatibility
✅ Fully backward compatible
-t/--aas-tokenflow remains unchangedaas_tokenoption still worksTesting