Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Blocking caller fails with exception toast being displayed

Aperta
  • Qualcosa non va?
#798 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
android, kotlin
Ambito
mobile, security

Direzione di ricerca

The payload names no source files, so start from the Call History overflow menu's block action and the SecurityException messages quoted in the report, which mention system, default dialer and current-user checks. Reproduce on a secondary Android user or with a non-default dialer, since the failure depends on the user and dialer role. Done means blocking succeeds for both users and the blocked numbers stay visible after switching tabs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug needs triage
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.

Lingua principale
Kotlin
Stelle
1.4k
Fork
213
Merge medio
5g 10h
PR unite (30g)
14

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di FossifyOrg/Phone

Tutte le issue di FossifyOrg/Phone

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.