TeamAmaze / TeamAmaze/AmazeFileManager
Large file copy from SMB to device storage doesn't work
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
As of v3.3.2
Copying a large 1.5G file from SMB to internal memory fails promptly, creates a smallish file with partial content.
The following copies work fine:
- large file (1.5G) from SMB to SD card (slow, but works)
- small files (~10K) from SMB to internal memory or to SD card
In summary, this is an issue only with large files and only from SMB to internal memory.
I believe this issue was in early versions, was fixed and copy worked with no caveats in most of 2018, then re-emerged with a recent update (probably the first update of several in Nov-Dec 2018).
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
Start by reproducing the reported copy scenarios on Android: a 1.5G SMB file to internal storage, the same file to an SD card, and a small SMB file to both destinations. No files or tests are identified in the issue; done means large SMB-to-internal-storage copies complete with the full file content, without regressing the working cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100