Crash on Graphene OS after entering server address: `No Activity found to handle Intent { act=android.intent.action.VIEW dat=HTTP:`

[Vrend]

⚠️ 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. Open app after installing
2. Enter address for my server
3. Click arrow to connect

Expected behaviour

It shouldn't crash; it should show the login prompt.

Actual behaviour

Crash with log (see below).

Android version

15

Device brand and model

Google pixel 8

Stock or custom OS?

Custom (explain in "additional information")

Nextcloud android app version

30300890

Nextcloud server version

30.0.5

Using a reverse proxy?

Yes

Android logs

Cause of error

Exception in thread "main" android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=HTTP://nextcloud.borgie.lan/... flg=0x10000000 }
    at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2448)
    at android.app.Instrumentation.execStartActivity(Instrumentation.java:2018)
    at android.app.Activity.startActivityForResult(Activity.java:5928)
    at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.kt:704)
    at android.app.Activity.startActivityForResult(Activity.java:5847)
    at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.kt:683)
    at android.app.Activity.startActivity(Activity.java:6395)
    at android.app.Activity.startActivity(Activity.java:6362)
    at com.owncloud.android.authentication.AuthenticatorActivity.launchDefaultWebBrowser(AuthenticatorActivity.java:493)
    at com.owncloud.android.authentication.AuthenticatorActivity.lambda$anonymouslyPostLoginRequest$1(AuthenticatorActivity.java:462)
    at com.owncloud.android.authentication.AuthenticatorActivity.$r8$lambda$HghPOrCvYiC9MbGZkBiQhXwJPi8(Unknown Source:0)
    at com.owncloud.android.authentication.AuthenticatorActivity$$ExternalSyntheticLambda9.run(D8$$SyntheticClass:0)
    at android.os.Handler.handleCallback(Handler.java:991)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loopOnce(Looper.java:232)
    at android.os.Looper.loop(Looper.java:317)
    at android.app.ActivityThread.main(ActivityThread.java:8826)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
    at com.android.internal.os.ExecInit.main(ExecInit.java:50)
    at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
    at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:369)

App information

• ID: com.nextcloud.client
• Version: 30300890
• Build flavor: gplay

Device information

• Brand: google
• Device: shiba
• Model: Pixel 8
• Id: AP4A.250105.002
• Product: shiba

Firmware

• SDK: 35
• Release: 15
• Incremental: 2025012700

Server error logs

Additional information

Running on Graphene OS version 2025012700 (latest)

[joshtrichards]

Exception in thread "main" android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=HTTP://nextcloud.borgie.lan/... flg=0x10000000 }

Are you entering HTTP (all caps) somewhere in your server configuration? Android requires lowercase here (for the intent).

Please see #14306 (comment)

[Vrend]

Yeah that'll do it. I had to override the protocol to "http" via environmental variable in docker. I originally had it as "HTTP" as that's how I've seen it done in online guides. This resolved my issue, thank you!

[joshtrichards]

I originally had it as "HTTP" as that's how I've seen it done in online guides.

Any idea what guide is suggesting that? (I'd like to see if I can get them to fix it since it's now come up twice in the last 30 days!).

[Vrend]

I believe I had just seen the name of the environmental variable across several forum posts (mostly relating to truenas), and had assumed the convention was to have the value be uppercase like the key and that it was effectively case insensitive.

I had to add this environmental variable because my container didn't allow me to login over http because the cookie was marked as "secure".