Auch nett: alle Dateien auf dem Mac tragen das Änderungsdatum "21.09.1667". Greift man über die BC iPad-App auf die Cloud zu, sieht man die korrekten Zeitstempel.
Boxcryptor for macOS 3.x Feedback
NoteBookUser You are absolutely correct.
In short: Both features ("download now" and "always keep local") are on our roadmap and we do want to offer them in the future.
A bit more elaborated: "Download Now" is offered by (and actually even independently managed by) Finder itself - not by us. It should work as expected (and for the large part of users we get feedback it also does), but there's a caveat: Finder can and does remove downloaded files from time to time according to heuristics that the documentation is not telling us. So when you "download now" and some time later the files got removed again, all we know is that Finder assumed you wouldn't need them anymore - but we get no explanation from Apple or Finder for that other than that this happens often when disk space is running low on the machine. Our response to that is that we are evaluating ways to counter that behaviour.
"Always keep local" is simply a new feature, and it's on our roadmap.
nathan Could you check if the error persists with the 3.11? That version is available at https://www.boxcryptor.com/en/download/macos/. If it does, please contact support@boxcryptor.com and we'll have a closer look at that.
Alex-ander If it doesn't even start any download, please contact us at support@boxcryptor.com to have a closer look at it. Best provide a screen sharing (command + shift + 5) with that so we can get a grasp of it right away.
If the files are removed again after a while when they were downloaded, please see https://boxcryptor.community/d/17455-boxcryptor-for-macos-3-x-feedback/85. We are already working on an improvement here.
Boxblue Could you record that issue (command + shift + 5) and contact us at support@boxcryptor.com with that? I'd like to have a closer look here.
Trebor_Returns Das würden wir uns gerne genauer ansehen. Könntest Du uns mit einem Screen-Recording (Command + Shift + 5) über support@boxcryptor.com kontaktieren?
Christian Mail ist unterwegs. Danke!
Christian Das selbe Problem habe ich auch mit der 3.11 auf macOS Ventura nachdem ich vor einigen Tagen auf ein McBook Pro 14" (M1 Pro) umgestiegen bin.
Davor hatte ich BC 2.46.1667 auf macOS Catalina (10.15.7) auf einem iMac (late 2012) laufen. Als cloud storage benutze ich OneDrive und den OneDrive sync client (sowohl Ventura als auch Catalina)
Auf dem Ventura-Rechner erscheinen alle Dateien im Boxcryptor mit dem Datum 21.09.1667. Auf dem Catalina Rechner haben alle Dateien das richtige Datum. Im OneDrive Ordnern auf beiden Rechner ist das Datum jeweils auch korrekt.
Dieses Problem ist bei Dateien, die schon auf OneDrive liegen. Wenn ich aber neue Dateien in den Boxcryptor-Ordner lege, dann bleibt das richtige Datum erhalten.
Das ist ein recht übler Bug, da ich ca. 12.000 Dateien auf OneDrive habe und alle das falsche und gleiche Datum haben.
Fozi Genau, die neu hochgeladenen Dateien tragen jeweils den korrekten Zeitstempel.
Haben Sie auch Probleme mit dem Download von Dateien? Bei mir werden schätzungsweise 2-5% der Dateien nicht ordnungsgemäß geladen.
Trebor_Returns Das konnte ich bisher nicht im Detail testen, da ich aufgrund des o.g. Themas BC momentan auf Ventura nicht nutze, sondern nur auf meinem Catalina Rechner. Dort läuft allerdings alles problemlos.
Trebor_Returns sorry I don’t speak German. I’ve seen this date issue with OneDrive too. My only solution was too link my OneDrive account to the Odrive sync provider which allows me to link the local Odrive synced folder to BC using a local file provider.
Hi
After two days of using this new version with my Dropbox account, the result is that I need to revert to the old one... lots of bugs and serious bugs:
- After moving some files from one folder to another, the BC kept crashing and restarting.
- Then I noticed an error report for Permission Mismatch, and the files that I had moved were reported as “not found”.
- I copy-pasted the files instead of moving as is suggested, but this led to a “conficted copy” version of the files.
- Decrypting a folder with many subfolders, finishes with no error report, but as it seems the process has done "some" of the decryption work, at some random portion of the contents
- Moved a folder "x" from a folder "z" under folder "y" using Boxcriptor. Boxcriptor drive shows x as a subfolder of y, Dropbox shows it as a subfolder of z. Loging out of Boxcriptor and login in again, shows x as a subfolder z (i.e. at its initial place)
- Opening a folder "x", automatically created a folder "x 2", showing all content of "x", while "x" is shown as empty
- Trying to copy or move files under a subfolder of depth 7 steps from root, causes an "provider internal error" and the operation stops, that is, I can do nothing with these files... I guess the problem has to do with the length of the file name due to the depth of the folder hierarchy.
This is not an acceptable situation for a release, I would suggest that you withdraw it until you test it thoroughly. We, as clients, are not supposed to do the alpha/beta testing for you
Manolis Koutlis
Dear BoxCryptor team, Robert, Christian,
Google shortcuts worked briefly in BC versions 2.** (MacOS Monterey). Now I have upgraded to BC version 3.11 (latest version) for MacOS Ventura. All shortcuts are not loaded in BoxCryptor. Due to sync issues, I am syncing thru Google Drive, and use BC with "local folder which uses the GD-sync location.
I am missing "tons of files" from Google Drive shortcuts, either created by myself, my team (share) or my partner (share). Totally unworkable this way.
When can we expect that BC is supporting GD shortcuts again?
- Edited
Dear BoxCryptor Team!
I reverted back to the old BoxCryptor after using the new version for a short while.
I simply need all my files stored locally on my drive and synced via iCloud. The only thing I need from BoxCryptor is encrypting my files before sending them to the cloud.
Once the new version was installed, BoxCryptor was perpetually syncing files, files were not available locally, when I wanted to simply copy decrypted files to an external drive, it took forever, since BoxCryptor obviously needed to download tons and tons of files beforehand, and all of this, while the encrypted version of the files was still available all the time on my local hard drive.
I have not fully understood, what the new BoxCryptor is doing to my files. But the experience was simply horrible.
Once I reverted back to the old version, things went back to normal. All my files are stored locally on my hard drive, encrypted in the cloud, synced by iCloud and encrypted / decrypted by BoxCryptor.
In case, the new version really is the way to go, I will look for an alternative.
Furthermore, BoxCryptor should describe in more detail, what is happening to the files with the new version. As I understand it, the files reside in the cloud, are synced by BoxCryptor itself, decrypted on demand and removed by Finder from the hard drive in an unpredictable manner.
I am really tech savvy, but I still cannot quite grasp it.
The experience with the new iOS app is likewise horrible. Each encrypted file has to be decrypted and loaded again and again, some files take ages to load, some never load at all.
Simply unacceptable. And again, I am not really sure what is happening, since the files are somehow kept in the cloud (iCloud? Some BoxCryptor Cloud?) and synced by BoxCryptor, but they are still somehow tied to my locally stored files on the Mac that reside on the hard drive and in iCloud and are only encrypted / decrypted by BoxCryptor.
Really confusing.
Kind regards
Sebastian
Dear Boxcryptor-Team,
I’ve had a similar experience as ThunderRoad. The new v3 on MacOS caused serious trouble on my machine, so that in the end I reverted to version 2. Issues I’ve noticed so far:
- Created/Modified timestamp of files are not preserved. Instead there was a random datetime of year 2077 or something visible in the finder. Newly created files/folders seemed to be correct. Timestamps are crucial for me, that was one of the reasons I left Cryptomator.
- Thats critical: At some point syncing stopped! I discovered this issue by chance, when I compared files on my iOS device with those on my Mac. That must not happen. If I had logged out of my Boxcryptor app on my Mac, all local file changes would have been lost. So I had so spend several hours comparing the file state on my Macbook with that in the cloud. (My setup: I had the OneDrive app running and pointed Boxcryptor to the local OneDrive folder since not all files in my OneDrive are encrypted.)
- I had an error saying, that it’s not possible to move an encrypted file into a non-encrypted folder or something. That error won’t go away, even if the file was already deleted. I think the previous point might be a result of this error.
- Encrypting and decrypting via creating copies is not nice, since timestamps are not preserved.
- The only positive thing for me so far: Spotlight is working again! But it only works on downloaded files, which brings me to the next point:
- There is no other way to force download all files apart from opening each single file. Even if I did that, it seemed to me that some files/folders were pushed back into the cloud again. I’d like to define which folders should permanently remain on my hard drive.
I didn’t dig deeper into those issues, because for me Boxcryptor should be a software I can rely on. Since v3 needs more time to get there, I went back to v2 and with that everything works as expected again.
[deleted]
Wann wird das Problem mit den falschen Zeit/Datumsstempel behoben?
I'm trying to stay all-in on v3, but without being able to see what is still sync'ing, it is getting challenging. I'm seeing cloud error icons (the cloud with the ! in it) but when I go to a different device, it looks like it sync'ed. Is there a roadmap item to show us remaining items to sync? I continue to be nervous that I'm making changes that aren't sync'ed. I think we all need confidence. Thank you for what you're doing around what Apple has done, but I agree with others that other products have found a way to get this fixed, so hopefully the team there is on their way.
Fozi Grund ist hier tatsächlich ein verändertes Verhalten durch ein MacOS Update. Finder ignoriert es, wenn wir sagen, dass wir ein Datum nicht kennen (nicht jeder Anbieter liefert uns das Erstellungs- / Modifikations-Datum). Früher wurde dann ein "-" dargestellt - jetzt zeigt Finder 1667 an...
Wir arbeiten an dem Problem.