no idea, that usually happens when the apk is modified or not installed directly from an unmodified playstore/gms. It doesn't only need to be the original playstore apk, it also needs to be installed from the original play store app (no backup restores, no aurora store, etc)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
no idea, that usually happens when the apk is modified or not installed directly from an unmodified playstore/gms. It doesn't only need to be the original playstore apk, it also needs to be installed from the original play store app (no backup restores, no aurora store, etc)
Originally posted by @1nikolas in https://github.com/1nikolas/play-integrity-checker-app/issues/62#issuecomment-3528828611
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue contains no runner file, test, entry point, or reproducible behavior; start by identifying which actions/runner failure this text is intended to report and whether the linked Play Integrity discussion applies. Before changing code, establish a runner-specific reproduction and define the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100