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

Specify source folder used in auto photo upload #177

Open
SailReal opened this issue Dec 27, 2019 · 13 comments
Open

Specify source folder used in auto photo upload #177

SailReal opened this issue Dec 27, 2019 · 13 comments
Labels
type:enhancement Improvements on an existing feature
Milestone

Comments

@SailReal
Copy link
Member

Description

As a user, I want to specify the source folder used in the auto photo upload to exclude some of them.

@SailReal SailReal added the type:enhancement Improvements on an existing feature label Dec 27, 2019
@SailReal SailReal added this to the Backlog milestone Dec 27, 2019
@cy2201

This comment has been minimized.

@SailReal

This comment has been minimized.

@cy2201

This comment has been minimized.

@SailReal

This comment has been minimized.

@bricktopdgp
Copy link

Any news after almost 2 years? Picture Upload is still not usable for all users who are using different folders for pictures.

@amigaosz
Copy link

I don't know if and what is planned in this case but it would be really nice if the user could secify more than one source folder to sync with the target vault and also set an individual vault as target or each source folder.

@LKJones83
Copy link

I don't know how to +1 this feature request, but I would like to +1 this feature request.

@phwi
Copy link

phwi commented Aug 1, 2022

Description

As a user, I want to specify the source folder used in the auto photo upload to exclude some of them.

Hi @SailReal I just tried Boxcryptor on android and had to deinstall it after 5 minutes when realizing that I cannot achieve my most important feature: I want to be able to do what "dropsync" is able to do, but just with encryption by Boxcryptor or an alternative - like Cryptomator.

I don't know if you know dropsync - it is legendary but unfortunately only works for dropbox. You can basically pick any folder on your android device and match it to any folder on your dropbox and dropsync will always and reliably sync both folders. If I delete something from one of the folders on my Desktop, it will be deleted from my smartphone. And sync algorithm is intelligent and avoids useless traffic. And very importantly it almost instantly realizes when something is changed. It is indeed a charm. However, nothing gets encrypted.

I'd like to have the awesome dropsync functionality in combination with cryptomator. But if I understand correctly Cryptomator is not even capable of syncing one single folder the way I described above for dropsync? What if my screenshots, my Google Lens PDF-scans, etc. all get stored in different locations on my Android Device and I cannot tell my photo app to store everything in the plain same folder? Then I won't be able to auto sync any of that with Cryptomator? And it will be the same hassle like with Boxcryptor where just a copy of a new photo get's uploaded but if I delete the photo from my android gallery this process won't be synced to the cloud resulting in a total chaos.

Sorry that I ask here but I'd like to avoid paying 10 EUR for the app, just to find out that it is not capable of doing any proper coded auto syncing. Unfortunately, it seems that there really is NO app on the market that is capable of doing any proper automated and fully synced 1:1 copy/syncing between multiple folders and devices and being also extremly secure with zero knowledge encryption at the same time...

@bricktopdgp
Copy link

No Cryptomator can not sync a folder....and for automatic photo upload you can Not choose which folder he should use nor it can handle subfolders...
Im waiting since some years for these features..

@czikus
Copy link

czikus commented Jan 12, 2023

I would also love to see this feature implemented. Many users surely use albums to organize their photos and without the ability to sync specific folders it becomes a huge mess and makes the photo sync unusable.

@NeverUsedID
Copy link

NeverUsedID commented Jun 24, 2023

This feature is required, otherwise it breaks the upload, when there are images in a folder where cryptomnator has no access.

Upload is working until cryptomater reaches the image files from whatapp, then there is a permissions error, because this specific folder can't be read by Cryptomator. Quick solution would be an option to ignore read errors on files/folders.

@SailReal
Copy link
Member Author

@NeverUsedID Did you give Photos and videos permission to Cryptomator?

@NeverUsedID
Copy link

NeverUsedID commented Jun 29, 2023

@NeverUsedID Did you give Photos and videos permission to Cryptomator?

Yes, i checked it again. As i said it works at the beginnining and uploads fotos, but after a while it stops with the permission popup. If i check the logs its always when it tries to upload Whatapp images. When it reaches this point even DCIM Fotos will not upload anymore. If i create a new vault, i can upload again until it reaches the whatapp folder. I also do not want to upload whatsapp, but i could live with it.

I 20230614105533.064 AutoUploadService Starting background upload I 20230614105533.097 ActivityLifecycle onResume org.cryptomator.presentation.ui.activity.BrowseFilesActivity@656f7f I 20230614105534.099 AutoUploadNotification Show storage permission required notification E 20230614105534.104 AutoUploadService Failed to auto upload image(s). org.cryptomator.domain.exception.FatalBackendException: java.io.FileNotFoundException: /storage/emulated/0/WhatsApp/Media/WhatsApp Documents/Connected_logo_original_final_transparent_png_2000x500.png: open failed: EACCES (Permission denied) at org.cryptomator.data.cloud.crypto.CryptoImplDecorator.writeShortNameFile(CryptoImplDecorator.kt:461) at org.cryptomator.data.cloud.crypto.CryptoImplVaultFormat7.write(CryptoImplVaultFormat7.kt:460) at org.cryptomator.data.cloud.crypto.CryptoCloudContentRepository.write(CryptoCloudContentRepository.kt:90) at org.cryptomator.data.cloud.crypto.CryptoCloudContentRepository.write(CryptoCloudContentRepository.kt:21) at org.cryptomator.data.repository.DispatchingCloudContentRepository.write(DispatchingCloudContentRepository.kt:149) at org.cryptomator.presentation.service.AutoUploadService.writeCloudFile(AutoUploadService.java:223) at org.cryptomator.presentation.service.AutoUploadService.upload(AutoUploadService.java:210) at org.cryptomator.presentation.service.AutoUploadService.upload(AutoUploadService.java:203) at org.cryptomator.presentation.service.AutoUploadService.upload(AutoUploadService.java:179) at org.cryptomator.presentation.service.AutoUploadService.lambda$startBackgroundImageUpload$1$org-cryptomator-presentation-service-AutoUploadService(AutoUploadService.java:111) at org.cryptomator.presentation.service.AutoUploadService$$ExternalSyntheticLambda1.run(Unknown Source:6) at java.lang.Thread.run(Thread.java:1012) Caused by: java.io.FileNotFoundException: /storage/emulated/0/WhatsApp/Media/WhatsApp Documents/Connected_logo_original_final_transparent_png_2000x500.png: open failed: EACCES (Permission denied) at libcore.io.IoBridge.open(IoBridge.java:574) at java.io.FileInputStream.<init>(FileInputStream.java:160) at java.io.FileInputStream.<init>(FileInputStream.java:115) at android.content.ContentResolver.openInputStream(ContentResolver.java:1516) at org.cryptomator.presentation.util.ContentResolverUtil.openInputStream(ContentResolverUtil.kt:20) at org.cryptomator.presentation.presenter.UriBasedDataSource.open(UriBasedDataSource.kt:18) at org.cryptomator.domain.usecases.cloud.CancelAwareDataSource.open(CancelAwareDataSource.kt:22) at org.cryptomator.data.cloud.crypto.CryptoImplDecorator.writeShortNameFile(CryptoImplDecorator.kt:433) ... 11 more Caused by: android.system.ErrnoException: open failed: EACCES (Permission denied) at libcore.io.Linux.open(Native Method) at libcore.io.ForwardingOs.open(ForwardingOs.java:563) at libcore.io.BlockGuardOs.open(BlockGuardOs.java:274) at libcore.io.ForwardingOs.open(ForwardingOs.java:563) at android.app.ActivityThread$AndroidOs.open(ActivityThread.java:7770) at libcore.io.IoBridge.open(IoBridge.java:560) ... 18 more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement Improvements on an existing feature
Projects
None yet
Development

No branches or pull requests

8 participants