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

Allow Android backups, again #5649

Closed
billie80 opened this issue Oct 30, 2021 · 14 comments
Closed

Allow Android backups, again #5649

billie80 opened this issue Oct 30, 2021 · 14 comments
Labels
stale An issue that hasn't been active for a while...

Comments

@billie80
Copy link

billie80 commented Oct 30, 2021

I found that after some discussion in this forum issue backup was disabled again in #5114.

I understand that there might be problems in cases like the one mentioned in the forum thread. Still there are other use cases where a backup is useful, as allowBackup not only allows for a google drive backup, it also makes it possible to do a local backup using adb backup or seedvault. It is true that backing up the sync target is not important as it is just a copy from the server. However it would be convenient to enable backup and restore of the App settings.

The forum thread mentions that it is not possible to control what is backed up however there is a method to do so. The attribute fullBackupContent in the Manifest file allows fine grained control (including and excluding files) over what is included in the backup and what is not. More information can be found here. As a reference the seedvault FAQ mentions an App (grote/Transportr@4dc38f4) for which this has been implemented. Here they were mainly concerned about the security of the backup as fullBackupContent also enables forcing an encrypted backup but it also shows how to backup only parts of the App storage.

It would be great to add backup support again for the App settings only.

If you think this needs to be discussed in the forum we can do so but I think it should not be necessary.

@ToddPerkins81
Copy link

I would like a backup option as well on Android. Currently sync isn't working for me on my phone anymore so it would be nice to have this feature.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 9, 2022

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label Jan 9, 2022
@billie80
Copy link
Author

billie80 commented Jan 9, 2022

Would be great if this could be implemented. Looking forward to feedback.

@JackGruber
Copy link
Contributor

As it looks at the moment, this is unlikely to happen

Android Backup is not an issue because it's not enabled, and probably won't.

https://discourse.joplinapp.org/t/is-my-joplin-master-password-being-exposed-to-google/22818/9?u=jackgruber

@billie80
Copy link
Author

billie80 commented Jan 9, 2022

I don't see why the arguments in this discussion should prevent the implementation of a backup method. I do not hope that Joplin is storing the password in plain text even if it is supposed to be in a secure location.
Also it could be stored in a separate file which is excluded from backup.
Additionally as I have written above it is possible to force encryption.
Furthermore it should be possible to allow only local backup and disable cloud backup. This way adb backup and Seedvault could work and no data is stored on someone elses computer.

@github-actions github-actions bot removed the stale An issue that hasn't been active for a while... label Jan 9, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2022

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label Feb 8, 2022
@billie80
Copy link
Author

billie80 commented Feb 8, 2022

Please leave it open. I think options are there which would satisfy all needs as well as meeting all concerns.

@github-actions github-actions bot removed the stale An issue that hasn't been active for a while... label Feb 9, 2022
@github-actions
Copy link
Contributor

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label Mar 11, 2022
@billie80
Copy link
Author

Same as above.

@github-actions github-actions bot removed the stale An issue that hasn't been active for a while... label Mar 12, 2022
@github-actions
Copy link
Contributor

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label Apr 11, 2022
@billie80
Copy link
Author

Bump.
Please anybody who has something to say tell me if there is a chance for this to be implemented or not. I think if properly implemented it should be possible but as I can not code I can only read the documentation and might be wrong.
If it wont be implemented I can live with it perfectly fine. This would also saving me time to keep this ticket alive.

@Daeraxa
Copy link
Collaborator

Daeraxa commented Apr 11, 2022

In terms of the settings there is a possibility this could be partially resolved by the settings sync GSoC idea (or if not for GSoC it remains on the "wish list" for somebody to implement later if they should want to).

See - https://joplinapp.org/gsoc2022/ideas/#14-client-settings-sync

@github-actions github-actions bot removed the stale An issue that hasn't been active for a while... label Apr 12, 2022
@github-actions
Copy link
Contributor

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label May 13, 2022
@github-actions
Copy link
Contributor

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale An issue that hasn't been active for a while...
Projects
None yet
Development

No branches or pull requests

4 participants