Work profile: unable to open account settings

[0xf104a]

Describe the bug When trying to open account settings via System settings nothing happens

To Reproduce Steps to reproduce the behavior:

1. Install microG to system(like in LineageOS4microG)
2. Flash system
3. Create work profile with Shelter
4. Log into your Google account
5. Go to System Settings > Accounts
6. Select tab "Work profile"
7. Select Google account
8. Click "Account settings" and observe that nothing happens

Expected behavior On step 8 it is expected that view with account settings would opened

System Android Version: 11 Custom ROM: LineageOS 18.1(PolarMod with microG)

Additional context

• UnifiedNlp(org.microg.nlp) is also installed on the system as I am not going to use any google stuff on main profile
• I have checked for the same issue in main profile, but there everything works fine

Also I have grabbed some logs which are generated when I am clicking on the "Account settings"(step 8):

E AccountTypePrefLoader: Refusing to launch authenticator intent becauseit exploits Settings permissions: Intent { act=com.google.android.gms.accountsettings.ACCOUNT_PREFERENCES_SETTINGS flg=0x10000000 (has extras) }

In my opinion the best fast-fix for this bug is to implement per-account access settings inside the microG core app itself.

[Atdtd]

Did you ever find a solution to this bug? Im having the same issue when trying to access account settings in my workprofile

[0xf104a]

Ok, not the solution, but workaround. I have logged out from my account, installed GMail(worked with microG at that time, have no idea whether it works now since my ROM already supports GrapheneOS GmsCompat) via AuroraStore and then logged in via GMail. After this I have tapped on my profile picture in GMail and then tapped "Account settings" and microG account settings has appeared. Summarizing you need to install any Google app which would work with microG and allows you to login to your account, use it to login into your Google account and then via this app access an account settings. This workaround was last tested in mid-January 2022

[Atdtd]

Thanks! This workaround still work.