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

binder: "intent:" target URIs that match multiple <service>s should only connect to the one of highest priority

Abierto
  • ¿Algo no está bien?
#12,490 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
android, java
Área
backend-api-design, mobile-dev

Línea de trabajo

Comienza siguiendo IntentNameResolver, el balanceador de carga pick-first y BinderClientTransport para entender cómo se seleccionan los servicios Android coincidentes y cómo los fallos de conexión activan el failover. El issue no proporciona nombres de archivos ni de tests; la tarea estará terminada cuando varios servicios coincidentes utilicen el servicio con mayor prioridad sin ocultar los fallos de conexión transitorios mediante un fallback no intencionado.

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

Descripción

binder

More than one <service> can advertise an <intent-filter> that matches a given Intent. IntentNameResolver returns all matches to the "pick-first" load balancer which tries them in priority order. If connecting to a first Service fails, pick-first will try the second highest priority Service.

Pick-first's fail-over behavior makes sense in the networked world where clients want to tolerate server failure and spotty connectivity. In the on-device context there are only two reasons we want fail-over:

  1. So an unauthorized app that maliciously gives itself a high <android:priority> can quickly be passed over by preauthorization, avoiding a denial-of-service situation.
  2. So multiple server apps in an <android:priority> hierarchy can independently collaborate on which of them is active by enabling/disabling only their own <service> components in PackageManager.

But BinderClientTransport can fail to connect for many transient reasons like:

  1. the phone/tablet is busy doing other things causing the server app to be slow to start (DEADLINE_EXCEEDED)
  2. the server app does many things other than host the target Service, and a bug in one of them crashes the whole process while the ServiceConnection is being established (UNAVAILABLE).
  3. the user "swipes away" the server app's actiivity from the "recents" UI just as the ServiceConnection is being established (UNAVAILABLE).
  4. the server app is manually/automatically updated to a newer version and android kills all its processes while the ServiceConnection is being established (UNAVAILABLE).

Fail-over for these other reasons is problematic because different AndroidComponentAddresss are likely different implementations of the requested interface. It would be like if you selected Chrome as your default mobile browser but when you clicked on a URL, your phone failed over to Firefox if it didn’t launch fast enough. Perhaps that’s better than failing to show the web page at all, but it's also masking the underlying problem with the explicitly configured first choice browser in a way that's surprising and non-deterministic.

Lenguaje dominante
Java
Estrellas
12.1k
Forks
4k
Merge medio
2 d 3 h
PR fusionados (30 d)
30

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 grpc/grpc-java

Todos los issues de grpc/grpc-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.