Blocking caller fails with exception toast being displayed

[josep11]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.11.1

Affected Android/Custom ROM version

Android 16 / Graphene OS 2026042100

Affected device model

Pixel 7

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

1. Open the app and gear towards the Call History tab.
2. Click the three dots for more options.
3. Click on the button that reads "block" the caller.
4. Confirm "Yes" on the modal.
5. Observe the behaviour.

Bonus: if navigating to another tab such as Favourites or Contacts and coming back to the Call History one, you will see the "blocked" numbers again.

Expected behavior

It shall be blocking the caller instead.

Actual behavior

It errors in different ways.

I reproduced the issue in two different users.

Admin user

When doing so from the admin user the error reads:

java.lang.SecurityException: Caller must be system, default dialer or defau...

Regular user

The user has got permissions to SMS and calls (from Graphene OS user management menu), and also it has permissions to access all the contacts, call history and calls.

When doing so from a regular user the error reads:

java.lang.SecurityException: The current user cannot perform this o...

Screenshots/Screen recordings

https://github.com/user-attachments/assets/1bf992b5-022b-4f0f-bcd9-5bbe4e011291
https://github.com/user-attachments/assets/f54a9a46-26ff-42cb-9142-e4ca77fe06d2

Additional information

I attach the logs, albeit they don't seem to contain any useful information.