Title: External Sites (navigation entries with app: "external") stopped opening on tap in 34.x — regression, works fine in 33.1.2

Abierto
#17,455 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Empieza reproduciendo el toque en el cajón de navegación lateral en 34.1.0; después, sigue cómo se gestionan las entradas no nativas con app: "external" y compara esa ruta con 33.1.2. Se considera terminado cuando las entradas tanto con redirect=true como con redirect=false se abren desde el cajón sin afectar a las entradas device-hidden.

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

Descripción

0. Needs triage bug
⚠️ Before posting ⚠️
  • This is a bug, not a question or an enhancement.
  • I've searched for similar issues and didn't find a duplicate.
  • I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
  • I agree to follow Nextcloud's Code of Conduct.
Steps to reproduce
  1. Configure at least one entry in External Sites (nextcloud/external), either Type: Link (redirect: true) or the default embedded type (redirect: false).
  2. Open the official Android app, log in, open the side navigation drawer.
  3. Tap the entry.
Expected behaviour

Entry opens — works in any browser, and in Android app 33.1.2.

Actual behaviour

On 34.1.0: row highlights (ripple), then nothing. Confirmed via server logs that zero HTTP requests ever reach the target — failure is entirely client-side, pre-network. Reproduces for every entry regardless of redirect true/false, icon, or target host.
What we ruled out

  • DNS/reachability — all hosts resolve publicly, work fine in browsers.
  • Server bug — found and patched nextcloud/external#769 (https://github.com/nextcloud/external/issues/769) (missing 'app' => 'external' in nav registration) ourselves; no effect on 34.1.0's behaviour.
  • Device targeting — device: browser-scoped entries correctly stay hidden on Android, so client detection still works.
  • Clean isolation: same server/account/entries — 33.1.2 works, 34.1.0 doesn't.

Couldn't get Logcat (OEM blocks main/system buffer reads on non-rooted ro.debuggable=0 builds), and no in-app logging option found in this version.

Android version

16

Device brand and model

Device: RedMagic 10S (NX789J), Android 16 (SDK 36)

Stock or custom OS?

Stock

Nextcloud android app version

App broken: 34.1.0 / App working: 33.1.2

Nextcloud server version

Server: Nextcloud 33.0.6 (snap), External Sites 8.0.1

Using a reverse proxy?

I don't know

Android logs

No response

Server error logs

Additional information

Additional context

34.1.0 released 2026-07-23; reproduces identically for both redirect true/false, suggesting a regression in how 34.x handles taps on non-native drawer entries in general, not something specific to External Sites' payload. Happy to provide the occ config:app:get external sites JSON or log excerpts on request.

Lenguaje dominante
Kotlin
Estrellas
5.6k
Forks
2k
Merge medio
1 d 21 h
PR fusionados (30 d)
101

Guía de contribución

Abrir la guía de contribución

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 nextcloud/android

Todos los issues de nextcloud/android

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.