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.

Sign up for GitHub

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

Jump to bottom

Request storage permission when configuring scheduled export location #188

Closed
7 tasks done
nep2ner opened this issue Nov 18, 2024 · 1 comment
Closed
7 tasks done

Request storage permission when configuring scheduled export location #188

nep2ner opened this issue Nov 18, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@nep2ner
Copy link

nep2ner commented Nov 18, 2024

Checklist

  • 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 feature request.
  • I have read and understood the contribution guidelines.
  • I optionally donated to support the Fossify mission.

Feature description

I want to configure scheduled export to go to a specific folder on my OS, that is synchronized off-device to another location. However because the app doesn't request storage permissions, I can't do this, it has to be the downloads folder.

Why do you want this feature?

The scheduled backups are not very useful if there isn't a way for me to get them off-device.

Additional information

No response
@nep2ner nep2ner added feature request Issue is about a new feature in the app needs triage Issue is not yet ready for PR authors to take up labels Nov 18, 2024
@Aga-C
Copy link
Member

Aga-C commented Nov 18, 2024

It's a duplicate of #144.

@Aga-C Aga-C closed this as not planned Won't fix, can't repro, duplicate, stale Nov 18, 2024
@Aga-C Aga-C added duplicate This issue or pull request already exists and removed feature request Issue is about a new feature in the app needs triage Issue is not yet ready for PR authors to take up labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Aga-C @nep2ner