"Save as" not work as expected
Check for existing issues
- [x] Completed
Describe the bug / provide steps to reproduce it
Today I find strange behavior (BUG) in menu option "Save as":
- select folder with origin file aka "Documents";
- change origin file name from "origin.txt" to "origin_new.txt";
- click ok, but..;
- in result new file name "origin_new.txt" not saved in "Documents" folder, but overwrited origin file ;(
android 12 acode 1.11.6(965)
p.s. now I understand why not planed this: Edit files with root permission? ยท Issue #1581 ยท Acode-Foundation/Acode - https://github.com/Acode-Foundation/Acode/issues/1581
@itmagpro Not able to Reproduce the issue. Is it possible to screen record the issue? ๐
@UnschooledGamer ofcourse
https://github.com/user-attachments/assets/a0ab2ada-d34b-4768-b5fe-33054bad68da
https://anonfile.co/rlbBeaw0y71WxjP/file
on screen record can see time rewrite origin file from 08:40 to 08:42 (in file prop + time on notification bar) and no new file in destination
...reopen dst folder and reboot dev not help :) file not present in dst folder and cant saved with new name in same folder with origin file.
IN OTHER LOCATION "Save as" ALSO SAVED ONLY WITH OLD NAME!
YES, ACODE THIS VERY DAGEROUS EDITOR...
SOME BUGGYDROM :)
@itmagpro , I could not reproduce the issue, I've attached a video (H.265 hoping your device can play it ๐). trying to reproduce it.
Let me know if anything was wrong while reproducing.
https://github.com/user-attachments/assets/f3834836-d33c-4fe7-a04f-dd9e6e034ff9
@UnschooledGamer :)
FOR REPRODUCE:
- open text file through Material Files file manager (NOT THROUGH ACODE FM) - https://f-droid.org/packages/me.zhanghai.android.files
- try Save as with new name
p.s. all permission for acode for access lninternal and external storage - granted! Not need root for save as new name? :)
other very BIG BUG is that acode fm not allow add root folder storage!!! Because when in storage root folder we have many many other folders with subfolders - then this VERY BIG GEMORROJ add each one by one...or for example when we attach sd-card and want direct edit (save as) files on sd-card in many some different folders
FOR REPRODUCE:
- open text file through Material Files file manager (NOT THROUGH ACODE FM) - https://f-droid.org/packages/me.zhanghai.android.files
- try Save as with new name
_p.s. all permission for acode for access lninternal and external storage - granted! Not need root for save as new name? :)
@itmagpro , it's a repro-able bug ๐, F-droid builds of Acode have all permissions feature accessible.
other very BIG BUG is that acode fm not allow add root folder storage!!! Because when in storage root folder we have many many other folders with subfolders - then this VERY BIG GEMORROJ add each one by one...or for example when we attach sd-card and want direct edit (save as) files on sd-card in many some different folders_
@itmagpro Choose Individual Folders to edit, This is intended behaviour for SAF to have scoped accesses. So that apps access only the folders their given access to. For Security.
All Files access are recommended by Android to be avoided mostly, And SAF Should be used. Only with Valid reasons or Valid incompatible reasons, All Files access could be used by a app.
So let me get this straight:
-
You opened a file
-
Edited it
-
Saved it with a different name
-
The new name was ignored, and the data was written to the file with the old name
Is that correct?
@RohitKushvaha01 yes, when:
- file opened through Material Files (other FM I not try)
- file located on internal storage (no mater)
- then new name was ignored, and the data was written to the file with the old name no any location and IN SAME LOCATION NOT GIVE WARNING ABOUT OVERWRITING ORIGIN FILE!
So let me get this straight:
1. You opened a file 2. Edited it 3. Saved it with a different name 4. The new name was ignored, and the data was written to the file with the old nameIs that correct?
@RohitKushvaha01 It's single SAF Mode. meaning a file opened from external app.
Hi there! ๐ We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Acode, please let us know by commenting on this issue(i.e Bump!), and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 14 days. Thanks for your help!
Seems now all worked fine, thanks for your job!!