ReadYouApp / ReadYouApp/ReadYou
Opening relative link crashes the app
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.5k
- Forks
- 330
- PR merge metrics
- No merged PRs in 30d
Description
1. Environment
- Device: [Samsung Galaxy S20 Ultra 5G]
- OS: [Android 14]
- APP: [0.11.1]
2. Describe the bug
Clicking on a relative link crashes the app.
Take this article:
https://blog.ploeh.dk/2024/12/30/pytest-is-fast/
Feed: https://blog.ploeh.dk/rss
There's this segment in the rss xml file:
As regular readers may have noticed, this is <a href="/2021/08/09/am-i-stuck-in-a-local-maximum">a bias that doesn't sit well with me</a>. Clearly, there are advantages to dynamic languages that I fail to notice. Is it <a href="/2024/12/09/implementation-and-usage-mindsets">a question of mindset</a>? Or is it a combination of several small advantages? </p> <p> In this article, I'll discuss another potential benefit of at least one dynamically typed language, <a href="https://www.python.org/">Python</a>.
Clicking on the first two links crashes the app, as they are relative.
This is the intent I got by setting link opening to "always ask" in settings and opening it in App Manager's Interceptor.
Any other setting just crashes the app.
URI intent:blank#blocked#Intent;scheme=about;launchFlags=0x3400000;end
VERSION 1
ACTION android.intent.action.VIEW
DATA about:blank#blocked
FLAGS 0x3400000
MATCHING ACTIVITIES 2
0 LABEL Interceptor
NAME io.github.muntashirakon.AppManager.intercept.ActivityInterceptor
PACKAGE io.github.muntashirakon.AppManager
1 LABEL Cromite
NAME com.google.android.apps.chrome.IntentDispatcher
PACKAGE org.cromite.cromite
Clicking on the third link (python) works just fine.
After clicking on the button at the bottom-right corner of the screen - "parse full content", all the links become clickable, even the first two.
Contributor guide
No contributing guide indexed for this repository
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 from the issue using an RSS item containing relative and absolute links, then trace the app's link-opening path for the relative-link case. Done means relative links open without crashing, absolute links continue to work, and links also work after parsing full content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100