TeamAmaze / TeamAmaze/AmazeFileManager
Failure to save file from Google Photos
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Android 11, Google Photos app, select photo, select Share, select Amaze File Manager (Save), within Amaze select target SMB network directory to save the photos to, press Save, popup message appears for a second saying the photo is being saved to the target directory. Result: nothing, photo file does not appear in the destination directory.
The same operation conducted within Amaze File Manager succeeds (i.e., locating and selecting the photo file within Amaze without going through Google Photos), saving to the same SMB network directory.
The same operation with Google Photos succeeds if a local directory is selected instead of the SMB network directory.
Amaze v3.7.0
Android 11, Moto G Power phone, current Google Photos
SMB destination: Win7 public folder, Amaze SMB link created with Win7 username/pwd
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Google Photos share flow described in the issue, comparing a local destination with the SMB network directory. Start by tracing the share/save handling and SMB destination behavior; done means a photo shared from Google Photos appears in the selected SMB directory, as it does for local destinations and Amaze-originated saves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 43/100