Deleted profiles leave app detritus/registration behind but unreachable

[cjtenny]

• I created and used secondary profiles to install apps.
• I deleted the profiles
• The apps were no longer visible to the owner as installed
• I created new profiles, then installed the same apps from before in those profiles.
• Installation was presented as "update to this existing application" for some of the apps that had been updated since installed in profiles that were deleted.

I don't know what remnants of those apps are around, but as mentioned they don't show up as installed applications to the owner profile.

Some of the profiles had the same name and passphrase as before; I deleted and recreated profiles to change their order in the profile selection drop-down.

[thestinger]

Did this happen on Android 11 or Android 12?

[cjtenny]

11

[thestinger]

You'll need to check whether this still happens for you on Android 12 GrapheneOS. It's currently in the Beta channel but you could wait until it's in the Stable channel. It will be in the next few days with the only substantial fix being that the next release will have the proper carrier configuration / APNs for Pixel 4a.

[cjtenny]

Got it, I will try to repro and update once 12 hits the 5a stable channel. Thanks for your work!

[thestinger]

Android 12 is now available in the Stable channel. Can you check if you still have this issue? I'd say it's about 50/50.

[cjtenny]

Will update tonight and try tomorrow then update here, unfortunately rather tuckered this evening. Thanks again!

[cjtenny]

Well, it didn't repro in 12, but I did uncover several other bugs - mostly likely upstream? - during the attempt to repro.

First, list of other bugs uncovered, then steps taken to attempt repro below:

Other notes from the update:

• Only owner profile received notification that system update had happened / reboot was needed
• Dark mode was turned off for all secondary profiles after update reboot
• GrapheneOS Keyboard automatically followed system use of dark theme for owner profile - but not other profiles
• Constant notifications in first new profile that 'sensors' permission being used by Setup Wizard long after setup complete, can't find app in recently used tray to close. Weirdly, didn't happen in 'garbage2' profile
• (Seems pretty major) "Back" swipe gesture not working in either newly created profile - at all. Pixel 5a.
• Super annoying, probably upstream, maybe 'feature' - newly created profiles appended to profile list in system settings view but inserted in arbitrary position in profile-switching view accessed from top menu. E.g. from repro steps below 'garbage' profile appeared in second position, 'garbage2' profile appeared in third position.

Attempted to reproduce. Steps:

• Create new profile ('garbage'), set up, assign PIN.
• Install latest f-droid in profile from f-droid.org via vanadium (allow vanadium to install)
• Install "Weather" by Beowulf version 3.03.2 (allow f-droid to install) (used 'versions' dropdown to select earlier version) (app not currently / never previously installed on this device)
• Open 'weather' app
• Switch to owner profile
• Delete 'garbage' profile
• Verify 'Weather' app now visible to owner in system 'all apps' (+ 'show system') view
• Create 'garbage2' profile, set up, assign different PIN
• Install latest f-droid in profile from f-droid.org via vanadium (allow vanadium to install)
• Install "Weather" by Beowulf - latest / default version 3.11(allow f-droid to install) X Observed regular install prompt rather than 'update to this existing application' prompt.
• Delete 'garbage2' profile since it didn't repro

Only thing different than before was that maybe using the same names & passphrases for profiles could've been related. I only thought of that after, maybe will try again later today.

Let me know if you want me to file separate issues for the other bugs encountered before closing this. Otherwise good to close.

[ghost]

Only owner profile received notification that system update had happened / reboot was needed

That's normal because only the owner profile can update the device.

GrapheneOS Keyboard automatically followed system use of dark theme for owner profile - but not other profiles

Likely separate keyboard settings for separate profiles. Anyways if this is a bug, GrapheneOS Keyboard is the stock AOSP keyboard which is very unmaintained and is going to be replaced. Should consider using a different keyboard. Florisboard is the future replacement for the AOSP Keyboard.