Repository navigation
On Android, quick capture sometimes is inserted into the currently open page rather than the journal #11464
Description
Search first
- I searched and no similar issues were found
What Happened?
On Android, when I share something from another app, Logseq is supposed to add a "quick capture" block to the journal. Most of the time, it does just that, but occasionally the block is inserted into a page I last viewed in Logseq.
I don't notice a pattern and can't tell when this happens. Sometimes I click on a link in Logseq, which opens a browser, from which I immediately share some quote, and it goes into the page I had open in Logseq. Other times, I'm just browsing the Internet and want to store something for later, and quick share is added onto a page I had opened half an hour ago or more.
The only constant is: quick captures are added either to the journal or to the last page I viewed.
Reproduce the Bug
I don't have a reliable reproducer, sorry about that.
Expected Behavior
Quick captures are inserted into the journal 100% of the time.
Screenshots
No response
Desktop or Mobile Platform Information
OnePlus 5T, Android 10, 0.10.9
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
Activity
Minoru commentedon Aug 8, 2024
Edited to fix the version: I was running 0.10.9, not the recent alpha build. (I thought I installed the alpha on both my computer and my phone, but apparently I only did it on the former.) I now installed 0.10.10 alpha 20240807 on both, and will report if the issue persists.
k1mbl3 commentedon Sep 12, 2024
I'm new to Logseq and the same thing just happened to me. It looks like when the app is still open in memory, it will dump the quick capture on that note; otherwise, it will happen in the journal
github-actions commentedon Mar 12, 2025
Hi There! 👋
We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!
If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.
Access additional Logseq 🚀 resources:
Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!
Minoru commentedon Mar 15, 2025
I'm running 0.10.10-alpha+nightly.20241216 and it behaves the way @k1mbl3 describes. I kind of learned to live with it by now. It's handy when I want to insert a link directly into some page. Still, I think it's a bug. I'd prefer Logseq to ask me every time where I want to insert the link.
github-actions commentedon Sep 14, 2025
Hi There! 👋
We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!
If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.
Access additional Logseq 🚀 resources:
Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!