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

Aperta
#17,455 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

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

Direzione di ricerca

Inizia riproducendo il tap nel drawer di navigazione laterale in 34.1.0, quindi traccia come vengono gestite le voci non native con app: "external" e confronta quel percorso con 33.1.2. Il lavoro è completo quando sia le voci con redirect=true sia quelle con redirect=false si aprono dal drawer senza influire sulle voci device-hidden.

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

Descrizione

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.

Lingua principale
Kotlin
Stelle
5.6k
Fork
2k
Merge medio
1g 23h
PR unite (30g)
101

Guida per i contributori

Apri la guida per i contributori

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

Tutte le issue di nextcloud/android

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.