EFForg / EFForg/apkeep

Stack overflow when using google-play source

Open
#238 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2.1k
Forks
161
PR merge metrics
No merged PRs in 30d

Description

OS: Windows 11 (build 26200.8655)
Command run: `apkeep -d google-play -a com.delphicoder.flud .`
Config file located at `%APPDATA%\apkeep\apkeep.ini` with CRLF line endings:
```ini
[google]
email = myEmail@gmail.com
aas_token = aas_et/...
```
Program output:
```
Downloading com.delphicoder.flud...

thread 'main' (29304) has overflowed its stack
```
One thing to note. I visited the Google [embedded setup page](https://accounts.google.com/EmbeddedSetup) to get my OAuth token. After agreeing to the terms, the loading never finished, so I grabbed the token from a POST request to `https://accounts.google.com/v3/signin/_/AccountsSignInUi/browserinfo`. Passed it to apkeep and it spitted out a normal-looking AAS token.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing `apkeep -d google-play -a com.delphicoder.flud .` on Windows with the shown `%APPDATA%\apkeep\apkeep.ini` credentials and token. Trace the google-play download and authentication entry points to identify the stack overflow; done means the command completes and downloads the APK without overflowing the stack.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authentication, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.