mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-26 21:05:55 +03:00
[GH-ISSUE #442] Clicking on links in mobile app causes the App to crash #208
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @EdSforzati on GitHub (Apr 26, 2020).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/442
Current behavior
When a link was created using the markdown link format
[text](url)and the link is then clicked in preview mode, the app crashes. See screenshot for crash.Screenshot
Expected behavior
Clicking on the link should open a browser or atleast ask which app to use to open the link.
Steps to reproduce
[text](url)Environment
Mobile
@Rokt33r commented on GitHub (Apr 26, 2020):
Thanks for the reporting. I'll fix it soon.
@Rokt33r commented on GitHub (Apr 26, 2020):
@WizardNo7
Did you put url without
http://orhttps://? I confirmed urls without the protocols causing the crash. If there are more cases causing the crash than this, please let me know.Anyway, I'll try to fix the case, using urls without the protocol prefixing.
@EdSforzati commented on GitHub (May 28, 2020):
Hey @Rokt33r , good catch.
It was in fact when not specifiying the protocol, only gooogle.com or www.google.com that was the issue.
@Rokt33r commented on GitHub (Aug 25, 2021):
Cannot reproduce the issue in the new mobile app. But I don't think the mobile app is covering every case. So if anyone notices that a similar problem happens again, please create a new issue.