Same Messages shows twice

[gouri-panda]

[Ashfaqbs]

"Hey folks, just jumping in to see if I can help with the 'invisible file' issue @gouri-panda is seeing.

Regarding the file not being searchable/visible despite physically existing: This usually happens when the MediaScanner isn't triggered after the write operation. On Android, just writing a file to disk doesn't automatically make it show up in Gallery or media queries immediately; the system database needs to be updated.

We likely need to call MediaScannerConnection.scanFile() (or the equivalent context broadcaster) on the final path once the download finishes. That should force the system to index it so it appears in other apps instantly.

And Since this keeps cropping up, maybe we can add an instrumentation test that explicitly attempts to query the file via MediaStore right after a mock download? That would fail in CI if the scanner logic breaks again."

[gouri-panda]

@Ashfaqbs isn't saving the folder in the download directory already calls Scanfile() method? So all we have to add the file in the download? Correct me if I'm wrong :)

[Ashfaqbs]

If we are using the Android DownloadManager API, then yes—it triggers the scan automatically. But if we are manually writing the file (using FileOutputStream or similar)—even if it is inside the Downloads folder—Android usually won't index it immediately. It essentially sits there as a 'ghost' file until the scanner happens to run later.

Since users are reporting that the file exists physically but isn't searchable/visible in other apps, it strongly suggests that the automatic link is missing.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐