"You do not have a browser installed" ... ???

[TheHippoMan]

I just installed "default-release v2.3.4 (1088) | Official Build" on my Android 13 device running Magisk Delta 23.6. I have put it into the Magisk Delta "Configure Mount" list, and it now is running as root.

When I go to Settings=>Manage Repos=>Update to Premium, I keep getting the following toast pop-up:

"You do not have a browser installed ..."

I indeed have multiple browsers installed on my device, and all of them are working fine in conjunction with all other apps.

I have changed the default browser over and over again to set each of these installed browsers as the default browser, but every time I set a new default browser, I keep getting that same "You do not have a browser installed ..." message when trying to upgrade to premium.

What do I have to do in order to get MagiskModuleManager to recognize that I indeed have a browser installed?

Thank you in advance.

[androidacy-user]

I just installed "default-release v2.3.4 (1088) | Official Build" on my Android 13 device running Magisk Delta 23.6. I have put it into the Magisk Delta "Configure Mount" list, and it now is running as root.

When I go to Settings=>Manage Repos=>Update to Premium, I keep getting the following toast pop-up:

"You do not have a browser installed ..."

I indeed have multiple browsers installed on my device, and all of them are working fine in conjunction with all other apps.

I have changed the default browser over and over again to set each of these installed browsers as the default browser, but every time I set a new default browser, I keep getting that same "You do not have a browser installed ..." message when trying to upgrade to premium.

What do I have to do in order to get MagiskModuleManager to recognize that I indeed have a browser installed?

Thank you in advance.

You are the only one so far who's reported this issue and we cannot reproduce, so we need you to install the latest debug GitHub Actions build and share logs from under debugging settings to help you.

[Daviteusz]

I have identical issue, logs from 2.3.5-debug:
logs.txt

[androidacy-user]

We've identified the issue, but it's considered low priority and will be fixed when we release the next update