APPLE: We want you all to use our iCloud storage. thats it.
You know the one. the one with all the outages and surveillance.
You know the one. the one with all the outages and surveillance.
Can’t you still mark them as online only if you aren’t using them? Did you read the Dropbox help article? It was more to do with apps not being able to download online only files if you try to open it with an app.And if your Dropbox account has terabytes of data in it, and you have a 500GB internal drive? That was the point of online only files.
OneDrive always performed worse for me on a Mac vs Dropbox. CPU and battery just got hammered. Hope they sort it for you!This has made OneDrive nearly unusable for me. The insane delay with opening folders, syncing changes, etc.
It makes my new M1 Pro MacBook Pro way slower than my 2013 MBP when working with files.
It's like every file system call is running through a OneDrive abstraction layer. All the lag of a web interface but with native Finder windows. Did they even test this before rolling it out into production? 12.3 won't be here for a while.
When the beta first launched it would skip the trash can when deleting files, is this still going on or have the fixed it? How about moving the OneDrive folder to a custom location, like an external drive? This was blocked in the original beta release, which seemed like a limitation of the API Apple is pushing on cloud providers. Any idea if this has been fixed? Has the online vs local files issue been fixed? Selecting online only for a top level folder wouldn't propagate throughout the full directory structure.I've been running the M1 native version of one drive since the beta came out, which includes the modern finder integration and I can say that it is AWESOME. no longer is one drive using tons of CPU and all the online vs local etc is native to finder similar to iCloud Drive, its a great upgrade!
Trash can is fixed and online vs local sub directories has been fixed as well.When the beta first launched it would skip the trash can when deleting files, is this still going on or have the fixed it? How about moving the OneDrive folder to a custom location, like an external drive? This was blocked in the original beta release, which seemed like a limitation of the API Apple is pushing on cloud providers. Any idea if this has been fixed? Has the online vs local files issue been fixed? Selecting online only for a top level folder wouldn't propagate throughout the full directory structure.
I think they mentioned about the external drive part in their blog post. There is a way: https://techcommunity.microsoft.com...es-on-demand-experience-on-macos/bc-p/3066588When the beta first launched it would skip the trash can when deleting files, is this still going on or have the fixed it? How about moving the OneDrive folder to a custom location, like an external drive? This was blocked in the original beta release, which seemed like a limitation of the API Apple is pushing on cloud providers. Any idea if this has been fixed? Has the online vs local files issue been fixed? Selecting online only for a top level folder wouldn't propagate throughout the full directory structure.
Sweet, thanks for answering, I'm a bit more encouraged about this API push then.Trash can is fixed and online vs local sub directories has been fixed as well.
Not sure about external drive location, haven’t tried myself
For the love of all that is holy, please use a tool like git, svn, mercurial, etc. Do not use file sync services to share source code between machines.The codes I changed in VS Code on my Mac almost reflect immediately on my work PC, which is on the other side of the globe.
Very excited for this. I'm using Onedrive from the App Store so I have to wait for the full release.I've been running the M1 native version of one drive since the beta came out, which includes the modern finder integration and I can say that it is AWESOME. no longer is one drive using tons of CPU and all the online vs local etc is native to finder similar to iCloud Drive, its a great upgrade!
Didn't Apple announce this API several years ago as a replacement for the crappy hacks that companies like Dropbox did to make their service work natively on macOS?Sounds like everyone is being forced to use the File Provider API? Box.com already uses this in their sync client. StrongSync also uses this tech as a 3rd party sync client for Dropbox, WebDAV, etc.
When your product digs its hooks so deeply into your computer that users can't upgrade their OS without fear of breaking it, you've made a bad product.This has been a problem since the release of Monterey. I just helped someone with this issue. The problems started after they upgraded from Big Sur to Monterey 12.0.1. The only fix was to wipe the iMac & reinstall Big Sur. Dropbox is now back to normal on this person's iMac running Big Sur. Thankfully the user didn't upgrade any of her other computers to Monterey & we told everyone else in the office to stay put on Big Sur.
I have OneDrive thru my Office365, I tried the app on my iMac and it ... sucked ... using the web interface only, sufficient for my needs
Maybe a hidden CSAM for third-party cloud storage enforcement by Apple.I wonder what 12.3 will include to change this
That's what my first thought was too. Side note: I tried Strongsync and it's really cool, but was riddled with bugs. I tried to contact the developer a few times but got no response. Too bad, it was a very cool concept, and was super fast.Sounds like everyone is being forced to use the File Provider API? Box.com already uses this in their sync client. StrongSync also uses this tech as a 3rd party sync client for Dropbox, WebDAV, etc.
I've been running the M1 native version of one drive since the beta came out, which includes the modern finder integration and I can say that it is AWESOME. no longer is one drive using tons of CPU and all the online vs local etc is native to finder similar to iCloud Drive, its a great upgrade!
I don't think so.I wonder if this will affect Google Drive?