ruffle-rs / ruffle-rs/ruffle-android
Crash when trying to open link while browser is disabled
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 569
- Forks
- 60
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 16
Description
I occasionally disable my browser to thwart me in wasting time on my phone. While playing a games yesterday, I accidentally tapped a link and Ruffle crashed. It was my first time using Ruffle on Android and I wasn't aware that I had tapped a link and assumed at first that Ruffle or the game I was playing was buggy. I quickly realized what was really going on, but in the first few moment I was a little bummed out.
Thanks a lot for Ruffle on Android! I enjoy being able to not grant the network permission (on GrapheneOS) to the app. It's very soothing, especially as I am ignorant about the potentially malicious capabilities of Flash games (though I do assume I'd probably be all fine ^^).
type: crash
osVersion: google/bluejay/bluejay:15/BP1A.250505.005/2025062700:user/release-keys
package: rs.ruffle:2506202, targetSdk 35
process: rs.ruffle
processUptime: 2900 + 233 ms
installer: org.fdroid.fdroid
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=https://www.nextplay.com/... }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2452)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:2021)
at android.app.Activity.startActivityForResult(Activity.java:5988)
at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.kt:675)
at android.app.Activity.startActivityForResult(Activity.java:5907)
at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.kt:660)
at android.app.Activity.startActivity(Activity.java:6455)
at android.app.Activity.startActivity(Activity.java:6422)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the crash on Android with browser handling disabled, using the reported ActivityNotFoundException as the starting point. Inspect the link-opening entry point and make sure an unavailable handler no longer crashes the app; verify the behavior with a link tap under the same conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100