[GH-ISSUE #1534] "Already hoarded" in Android app due to exotic link schema? #958

Open
opened 2026-03-02 11:53:59 +03:00 by kerem · 4 comments
Owner

Originally created by @Syndesi on GitHub (Jun 6, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1534

Describe the Bug

Trying to add different links of the website winfuture.de, which uses an exotic link schema, results in an "already hoarded" message on the Android app for all links after the first one.
The link schema of said website is a bit exotic:

  • https://winfuture.de/news,151396.html Link
  • https://winfuture.de/news,151404.html Link

I am able to add them to Karakeep via its web UI just fine, but adding them via the Android app only works for the first link, and after that the App tells me, that the new link is "already hoarded".
Maybe it's due to some link sanitization code?
Could also be related to #513

Steps to Reproduce

  • open https://winfuture.de/news,151396.html Link in the browser
  • share first website with the Karakeep App, which should work
  • open https://winfuture.de/news,151404.html Link in the browser
  • share second website with the Karakeep App, which should say "already hoarded"

Expected Behaviour

Karakeep should support exotic but valid link schemas not only in its web UI, but also its Android app.

Screenshots or Additional Context

No response

Device Details

Motorola Edge 30, Android 14 / LineageOS 21

Exact Karakeep Version

1.6.9 (app), v0.23.2 (web ui)

Have you checked the troubleshooting guide?

  • I have checked the troubleshooting guide and I haven't found a solution to my problem
Originally created by @Syndesi on GitHub (Jun 6, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1534 ### Describe the Bug Trying to add different links of the website `winfuture.de`, which uses an exotic link schema, results in an "already hoarded" message on the Android app for all links after the first one. The link schema of said website is a bit exotic: - `https://winfuture.de/news,151396.html` [Link](https://winfuture.de/news,151396.html) - `https://winfuture.de/news,151404.html` [Link](https://winfuture.de/news,151404.html) I am able to add them to Karakeep via its web UI just fine, but adding them via the Android app only works for the first link, and after that the App tells me, that the new link is "already hoarded". Maybe it's due to some link sanitization code? Could also be related to #513 ### Steps to Reproduce - open `https://winfuture.de/news,151396.html` [Link](https://winfuture.de/news,151396.html) in the browser - share first website with the Karakeep App, which should work - open `https://winfuture.de/news,151404.html` [Link](https://winfuture.de/news,151404.html) in the browser - share second website with the Karakeep App, which should say "already hoarded" ### Expected Behaviour Karakeep should support exotic but valid link schemas not only in its web UI, but also its Android app. ### Screenshots or Additional Context _No response_ ### Device Details Motorola Edge 30, Android 14 / LineageOS 21 ### Exact Karakeep Version 1.6.9 (app), v0.23.2 (web ui) ### Have you checked the troubleshooting guide? - [x] I have checked the troubleshooting guide and I haven't found a solution to my problem
Author
Owner

@ovizii commented on GitHub (Sep 7, 2025):

I am not sure if I have the exact same issue but sometimes, when I share a link on Android with karakeep, karakeep pops up and says: already hoarded. Thinking that I might have bookmarked the link a while ago and forgotten, I go on about my business only to realize later, that the link hasn't actually been hoarded at all. I haven't paid attention to the link structure like OP so far.

So whenever I see “already hoarded” I repeat the hoarding again and sometimes I see:
A) already hoarded again, which most of the time turns out to be true
B) the success message about the link being hoarded (which is also true)

This makes me distrust the app and makes me hoard everything twice.

Xiaomi k20, custom ROM (Evolution X), Android 15
karakeep Android version 1.7.0
karakeep via docker 0.26.0

<!-- gh-comment-id:3263761258 --> @ovizii commented on GitHub (Sep 7, 2025): I am not sure if I have the exact same issue but sometimes, when I share a link on Android with karakeep, karakeep pops up and says: already hoarded. Thinking that I might have bookmarked the link a while ago and forgotten, I go on about my business only to realize later, that the link hasn't actually been hoarded at all. I haven't paid attention to the link structure like OP so far. So whenever I see “already hoarded” I repeat the hoarding again and sometimes I see: A) already hoarded again, which most of the time turns out to be true B) the success message about the link being hoarded (which is also true) This makes me distrust the app and makes me hoard everything twice. Xiaomi k20, custom ROM (Evolution X), Android 15 karakeep Android version 1.7.0 karakeep via docker 0.26.0
Author
Owner

@xuatz commented on GitHub (Sep 9, 2025):

From @Syndesi's description, I think his reported issue might be separate, but @ovizii, the problem you described (#513) is known and I have been testing a potential fix. It appears to improve the situation but not completely.

including the fix + dismissing after hoarding and exit/closing the app after that seem to give me a ballpark 5% "already hoarded" bug occurrence rate. From the perspective of the general android users, I think 95% success rate is still unacceptable, but for my personal use it's good enough.

The package we are using expo-share-intent isn't perfect for our needs anyways, because ideally (in my opinion), we probably should be able to share/hoard to karakeep without having to open the app. So maybe implementing the share intent handling by hand would be the long term solution to this problem.

<!-- gh-comment-id:3272511523 --> @xuatz commented on GitHub (Sep 9, 2025): From @Syndesi's description, I think his reported issue might be separate, but @ovizii, the problem you described (#513) is known and I have been testing a [potential fix](https://github.com/karakeep-app/karakeep/pull/1762). It appears to improve the situation but not completely. including the fix + dismissing after hoarding and exit/closing the app after that seem to give me a ballpark 5% "already hoarded" bug occurrence rate. From the perspective of the general android users, I think 95% success rate is still unacceptable, but for my personal use it's good enough. The package we are using `expo-share-intent` isn't perfect for our needs anyways, because ideally (in my opinion), we probably should be able to share/hoard to karakeep without having to open the app. So maybe implementing the share intent handling by hand would be the long term solution to this problem.
Author
Owner

@ovizii commented on GitHub (Sep 10, 2025):

Thanks for confirming I wasn't imagining things ;-)
I'll subscribe to the linked issue to stay on top of news.

<!-- gh-comment-id:3275694927 --> @ovizii commented on GitHub (Sep 10, 2025): Thanks for confirming I wasn't imagining things ;-) I'll subscribe to the linked issue to stay on top of news.
Author
Owner

@jersam commented on GitHub (Oct 6, 2025):

I get already hoarded all the time, I send it twice and the 2nd time it goes through.

Using cloudflare, npmplus

<!-- gh-comment-id:3372047698 --> @jersam commented on GitHub (Oct 6, 2025): I get already hoarded all the time, I send it twice and the 2nd time it goes through. Using cloudflare, npmplus
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#958
No description provided.