MuntashirAkon / MuntashirAkon/AppManager

Incorrect decoding of the `AndroidManifest.xml` parameter `android:backgroundPermission`

Open
#2,040 0 comments 0 reactions 0 assignees View on GitHub
Bug Priority: 2 Severity: 1 Status: Pending
Dominant language
Java
Stars
9k
Forks
518
PR merge metrics
No merged PRs in 30d

Description

### Please check before submitting an issue

- [x] I know what my device, OS and App Manager versions are
- [x] I know how to take logs
- [x] I know that generating a report, in whole part or in part, using AI/LLM is prohibited
- [x] I know how to reproduce the issue which may not be specific to my device

### Describe the bug

Whilst viewing the ‘Android System’ app manifest, I noticed that `android:backgroundPermission` had been decoded as `android:autofillSaveCustomSubtitleMaxHeight`

### To Reproduce

_No response_

### Expected behavior

_No response_

### Screenshots

_No response_

### Logs

_No response_

### Device info

- Device: Redmi Note 9 Pro
- OS Version: Android 12, MIUI 14
- App Manager Version: 4.1.0
- Mode: NonRoot

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the decoding of android:backgroundPermission while viewing the Android System manifest in App Manager. Trace the manifest-attribute mapping used for that parameter and compare it with the decoded android:autofillSaveCustomSubtitleMaxHeight value. Done means the manifest displays android:backgroundPermission with the correct decoded value.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.