Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Blocking caller fails with exception toast being displayed

Abierto
  • ¿Algo no está bien?
#798 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
android, kotlin
Área
mobile, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Kotlin
Estrellas
1.4k
Forks
213
Merge medio
5 d 10 h
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FossifyOrg/Phone

Todos los issues de FossifyOrg/Phone

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.