I will present a bug report on a App Management app. After reading the report, please explain why the author of this report considers the app's behavior to be a bug. Then, determine if this bug is related to common sense and whether it can be identified by users who don't possess any specialized knowledge of the app. The bug report is as follows: "Some Permissions and App Ops Revert Back. Describe the bug

Can't get changes to (some) App Opps to persist.

To Reproduce

1a. Go to App Opps tab in an app. Disable (particularly interested in these) 63 RUN\_IN\_BACKGROUND and 48 WRITE\_WALLPAPER. Refresh and note that both permissions jump back to enabled.

1b. With the package list displayed, go to "1-Click Ops", and select "Set mode for app opps...". Enter 63 in the "Input app ops" field and "allow" in the "Mode" field. List of apps appears. Uncheck apps that should not run in background. Apply. App pages still display permission as enabled.

Expected behavior

Would like a permission to stay off when I turn it off. :)

Device info

Device: multiple (will mention two Samsung Galaxy Tab 2 and Teclast T20).
OS Version: Android 6, 7, and 10
App Manager Version: [2.6.4]
Mode: root
Additional context

The filtering search of "Set mode for app ops..." seems completely random. Some apps appear in both Mode Allow and Mode Ignore, and some of those appear with the check box selected when filtered by Allow, yet unselected when filtered by Ignore."
user
As per your bug report, it appears that the author of the report is facing the issue of some app permissions and App Ops not persisting after disabling them. The bug report includes steps to reproduce the issue and also mentions the expected behavior. Therefore, based on this information, it appears to be a valid bug report, where the app is not functioning as expected.

Regarding your additional context, it seems that the filtering of the Set mode for app Ops option is unpredictable. However, this information is not directly related to the main bug. This issue may be caused due to any of the permissions you mentioned.

This bug can't be identified by users who don't possess any specialized knowledge of the app. Technically, a bug related to permissions should not be visible to regular users, as the app's logic is located in the app's background section. A bug related to application operation settings should only be noticed by developers and expert users.

Additionally, it is recommended that you run the app within the standard conditions and settings to identify most bugs' root cause. An Application’s developed settings or the usage of medium will differ, and the same bug might occur unexpectedly. Ensure to provide the app using its current configuration because it conveys the way in which the bugs and errors function.

Also, consider what you're attempting to attain due to the accidental operation rather than analyzing the source code. Using an over-experienced perception, the single answer to problems is to study the 'why.' But Windows File Administration allows you to avoid dozens of snags even when you're uninformed of what you're attempting.

In conclusion, it appears to be a reasonable and specific bug report, and based on the provided information, they're authentic. You've given all the technical data that users would need to replicate. A developer may create a new ticket that the client may monitor for you, and fixing your issue takes a little while, but at least you know they're functioning on it.
assistant
I will present a bug report on a App Management app. After reading the report, please explain why the author of this report considers the app's behavior to be a bug. Then, determine if this bug is related to common sense and whether it can be identified by users who don't possess any specialized knowledge of the app. The bug report is as follows: "Some Permissions and App Ops Revert Back. Describe the bug

Can't get changes to (some) App Opps to persist.

To Reproduce

1a. Go to App Opps tab in an app. Disable (particularly interested in these) 63 RUN\_IN\_BACKGROUND and 48 WRITE\_WALLPAPER. Refresh and note that both permissions jump back to enabled.

1b. With the package list displayed, go to "1-Click Ops", and select "Set mode for app opps...". Enter 63 in the "Input app ops" field and "allow" in the "Mode" field. List of apps appears. Uncheck apps that should not run in background. Apply. App pages still display permission as enabled.

Expected behavior

Would like a permission to stay off when I turn it off. :)

Device info

Device: multiple (will mention two Samsung Galaxy Tab 2 and Teclast T20).
OS Version: Android 6, 7, and 10
App Manager Version: [2.6.4]
Mode: root
Additional context

The filtering search of "Set mode for app ops..." seems completely random. Some apps appear in both Mode Allow and Mode Ignore, and some of those appear with the check box selected when filtered by Allow, yet unselected when filtered by Ignore."
user
The author of the report considers the app's behavior to be a bug because the changes they make to the App Ops permissions do not persist. Specifically, when they disable certain permissions such as "RUN_IN_BACKGROUND" and "WRITE_WALLPAPER", these permissions revert back to being enabled after refreshing the page or applying the changes. The author also notes that this behavior occurs across multiple devices and OS versions.

This bug is related to the app's functionality and not necessarily to common sense. A user without specialized knowledge of the app may not immediately identify this as a bug, as they may assume that certain permissions cannot be disabled or that the app is designed to revert changes for security reasons. However, if a user notices that their changes are not being saved and the app is not behaving as expected, they may suspect that there is a bug.

In any case, it is important for the app developers to address this issue and ensure that the App Ops permissions can be properly managed by users.
assistant