Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to download a photo from memories to my phone #1155

Open
yurividal opened this issue Apr 22, 2024 · 5 comments
Open

Unable to download a photo from memories to my phone #1155

yurividal opened this issue Apr 22, 2024 · 5 comments
Labels
android NativeX / Android bug Something isn't working
Milestone

Comments

@yurividal
Copy link

yurividal commented Apr 22, 2024

Describe the bug
I cam browse and upload images to my memories just fine. But, when I click "download" on any image, nothing happens. The image is not downloaded to my phone, and no error or warning message is shown on the app.

Clicking the "share" button, shows a loading animation forever. Nothing happens.

I also noticed that if I go to the app settings, under notifications, it says "all notifications from this app are blocked" and doesn't allow me to change it to on. Not sire if this is related.

To Reproduce
Check video screenshot bellow:

Screenshots

Screen_Recording_20240422_061221_Settings.mp4

Platform:

  • OS: android 14 (Samsung OneUI 6.1)

  • Memories Version: 7.2.0

  • Nextcloud Version: (28.0.3)

  • PHP Version: 8.2.16

  • No errors on any of the docker containers

  • Download works fine using memories on a browser

  • Download works fine using the nextcloud official app.

Here is some adb logs i collected. (Seems to be a permission thing? maybe old target sdk?)

04-22 07:26:53.892 12459 13019 W DownloadManager: Path appears to be invalid: /storage/emulated/0/Download/memories/file_name.jpg
04-22 07:26:53.960 12459 21423 W DownloadManager: [105] Stop requested with status HTTP_DATA_ERROR: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
04-22 07:26:53.961 12459 21423 D DownloadManager: [105] Finished with status WAITING_TO_RETRY
04-22 07:26:53.961 12459 21423 V DownloadManager: MIME Type = null
04-22 07:26:53.971 12459 21423 I DownloadManager: Download 105 finished with status WAITING_TO_RETRY
04-22 07:26:53.971 12459 13401 I DownloadManager: Notification Clear Download 1:gallery.memories
04-22 07:26:53.973  2504  2504 D NotificationService: CancelNotificationRunnable end r = 0|com.android.providers.downloads|0|1:gallery.memories|10066, reason = 8
04-22 07:26:53.974 12459 12459 D DownloadManager: onStopJob id=105, reason=cancel() called by app, callingUid=10066 uid=10066 jobId=105
04-22 07:26:53.976  2504  7506 W JobScheduler: Job didn't exist in JobStore: f40f242 #u0a66/105 DownloadManager:com.android.providers.downloads

Edit:
I am running nextcloud in my internal lan, with a self-signed certificate. Could that be the issue?

04-22 07:36:40.978 12459 24798 W DownloadManager: [106] Stop requested with status HTTP_DATA_ERROR: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
@yurividal yurividal added the needs triage To be triaged label Apr 22, 2024
@yurividal
Copy link
Author

edit: i've edited the report to add some adb logs i collected

@pulsejet pulsejet added bug Something isn't working android NativeX / Android and removed needs triage To be triaged labels Apr 22, 2024
@pulsejet pulsejet added this to the 7.3 milestone Apr 22, 2024
@yurividal
Copy link
Author

@pulsejet I am convinced this is being caused by the self-signed cert. Downloadmanager seems to be rejecting the untrusted CA, even though I have the CA cert installed as a trusted chain.

@pulsejet
Copy link
Owner

Yeah, that's very likely

@pulsejet pulsejet modified the milestones: 7.3, 7.4 Apr 30, 2024
@Termikkazan
Copy link

I still have this problem. self-signed certificate. The smartphone's built-in bootloader cannot download files. if you copy the link from the download manager and open it in the browser, it will display "{"message":"Not found (handle)"}". But I also noticed that when the files are downloaded normally into the browser version. and if you follow the link of the downloaded file again, then “{"message":"Not found (handle)"}" will also be displayed. As I understand it, when we download files, a temporary link ".../memories/api/download/xxx" is created with the ability to download the file one time. possible for one thread. And the built-in bootloader may use multithreading. Isn't that the problem?
PS. Sorry. I am not an English speaker, I use a translator.

@pulsejet
Copy link
Owner

Yes, this bug isn't resolved. It needs a major rewrite of the download logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
android NativeX / Android bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants