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

Edit, "Keep old change date" not working #154

Closed
7 tasks done
secretmango opened this issue Mar 1, 2024 · 1 comment
Closed
7 tasks done

Edit, "Keep old change date" not working #154

secretmango opened this issue Mar 1, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@secretmango
Copy link

Checklist

  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected app version

1.1.1

Affected Android/Custom ROM version

GrapheneOS Android 14

Affected device model

Pixel 6a

How did you install the app?

GitHub releases

Steps to reproduce the bug

In settings, enable "keep old date on file operations"

Change a file, save it under the same name (remove the _1, regular way expected when editing a file), check its metadata

Expected behavior

The file metadata should not change

Actual behavior

The file is created new with its "created" metadata being the same as "last changed".

It is not actually edited it seems, at least when "editing a file" i.e. overiting the existing file.

Screenshots/Screen recordings

No response

Additional information

No response

@secretmango secretmango added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Mar 1, 2024
@Aga-C
Copy link
Member

Aga-C commented Mar 1, 2024

It's another case of an already raised bug about losing metadata: #29.

@Aga-C Aga-C closed this as not planned Won't fix, can't repro, duplicate, stale Mar 1, 2024
@Aga-C Aga-C added duplicate This issue or pull request already exists and removed bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants