App settings bug when going into an app through Settings > Apps in Owner

yore

In the Owner profile, going to Settings > Apps and pressing on any app installed only in a secondary profile causes Settings to misbehave and the screen repeatedly flickers until the Settings app is closed. Using a Pixel 7 Pro with the latest stable release.

Any workarounds?

other8026

yore I am not experiencing this. Have you updated to the latest version, 2023101300, from yesterday / earlier today?

yore

other8026 Yes I am running the latest stable release from today (2023101300). The issue is still there and only occurs on app settings installed in secondary profiles but not in Owner.

other8026

yore That's strange. I just updated to the latest release and I'm still not able to reproduce the issue.

This is sure to sound like a dumb suggestion, but have you restarted your phone and it still does this?

Since this is a weird issue for a system app, I'd suggest you try to repeatedly make the settings app crash. If possible, try a few times to get the system to display a crash popup. Show the details of the crash and report them in the GrapheneOS issue tracker: https://github.com/GrapheneOS/os-issue-tracker/issues

[deleted]

other8026 Someone reported the same issue
https://github.com/GrapheneOS/os-issue-tracker/issues/2495

The issue was closed despite OP said the issue is not resolved.

I am having the same issue which i posted here
https://discuss.grapheneos.org/d/8161-screen-flickers-on-opening-app-info-of-app-installed-in-secondary-profile

yore

other8026 I restart multiple times per day. Looks like it's an upstream issue but hopefully a fix is released soon.

de0u

[deleted] The issue was closed despite OP said the issue is not resolved.

Not exactly. It was closed at a time when the OP wasn't running the current release, and the OP's non-resolved report happened after the closure.

Meanwhile, the issue is not merely closed. It is marked as "upstream", meaning that it is inherited from AOSP. Also, a workaround is listed.

So, the issue is not fixed, but it is also not closed over the objection of the person who raised it. And there is reason to hope that Google will fix it.

Please note that I do not speak for the GrapheneOS project.