Feb 01 2022 12:04 PM - edited Feb 24 2022 10:21 AM
Hello there!
2.24.22 UPDATE: We've been listening to your feedback, and we've made some design changes. We're releasing a new version that addresses the most common themes and makes it easier to achieve the previous experience. Please read the latest blog post for more details.
Two weeks ago, we posted an update about Files On-Demand for macOS and have received overwhelming feedback from the community. We have spent a lot of time reading your comments and concerns to understand how we can improve your experience on macOS. To address some of the common issues and doubts we have updated the blog with a FAQ. If you still have more queries feel free to reach out to the team directly on this thread.
Thank you for your constant support and partnership!
Team OneDrive
Feb 09 2022 03:21 AM
I agree 100%, and it's nice to see that you named DEVONthink there. I also use this program with indexed files that are in my OneDrive folder, and I am very nervous about something going wrong. Do you have any information/suggestions about dealing with this issue in DEVONthink?
Also, what exactly is the situation with other Cloud services i.e. Dropbox? I have read that they will also experience problems, esp. with Monterrey 12.3, but do you know if other cloud storage/sync providers have developed solutions to this?
Thanks!
Feb 09 2022 05:43 AM - edited Feb 09 2022 05:46 AM
@YaYaTurre There has recently been a thread at DEVONtechnologies' forum about the impact that the changed behaviour of OneDrive may have on DEVONthink if you are indexing files. DT's development team does not consider this to be a significant issue currently as they have mechanisms in place to detect broken paths to files but there is no definite official stance on this yet. The thread is on community forums here.
Most of my databases have imported files (except for one database, which also indexes files in OneDrive and which has been fine so far), so if you are concerned about this, for the time being, you may consider switching to importing instead of indexing files. However, I don't think you would lose any files indexed in DEVONthink, and everything will probably be fine, should anything happen, when you fix/update the path to indexed files. The worst that can (probably) happen is that the files would be unavailable to DT until "downloaded" from OD's cache again.
However, I agree that the new OD behaviour results in an uncomfortable uncertainty if you just want to make sure your files are local and available to all the apps you may be using.
Dropbox is currently in beta with the Apple Silicon optimised client, and they have said that they will have more information on the impact of macOS 12.3 and File Provider when the next beta rolls out in March.
Google Drive currently works fine, as it does not rely on deprecated Kernel extensions, so it may not be impacted by changes (this remains to be seen). Still, it's 'all or nothing' there as the new client has lost the selective sync ability when it was released last year, so you either use file streaming (= files on demand) or sync everything to the Mac (you cannot select just a couple of folders).
However, there also seem to be issues around Spotlight and indexing; see this on Google Cloud Community forums. The way I understand this, this impacts primarily files that are streamed and not available locally, similar to current OneDrive issues. I have not been actively using Google Drive for a couple of years now, but I have just tested it in the past week and Spotlight seems to be indexing and finding files that have been mirrored locally i.e. downloaded to the Mac.
Feb 09 2022 05:49 AM
Hi@dario_s!
Thanks so much for your detailed and extremely helpful reply. I really appreciate it. Good luck with everything!
/YaYaTurre
Feb 10 2022 01:41 PM
Feb 11 2022 02:37 PM
Feb 11 2022 06:07 PM - edited Feb 11 2022 07:38 PM
I have run some tests. As I understand reading what @Jack Nichols has written in the post explaining everything, the Files on-demand experience used now in OneDrive uses Apple’s File Provider platform, a new api offered by the OS that is replacing an older kernel extension that OneDrive was previously using. Isn't this the same api used by iCloud Drive to maintain the syncing of its contents on macOS with the cloud? Then why does iCloud Drive offer a seamless experience and isn't affecting the indexing of the Spotlight search service on macOS for files stored on it from other devices?
This just looks to me like a very poor implementation of the solution by Microsoft.
Just run a short test if you want to try this:
- Create any text document on iPhone and save it to iCloud Drive (a Word document works fine).
- After this go to the Mac and use Spotlight to search for a word inside that document. As you can see Spotlight shows you the created document on the results. It is not only indexing the document by filename without any problems but also its contents.
Try to do the same with OneDrive and the process fails miserably.
I have set the whole OneDrive folder to Always keep on this device. If all the files are already been downloaded to a cache, why isn't OneDrive just transferring them to the OneDrive root folder automatically so Spotlight can index them properly? The files are clearly in the local disk already, this is easy to see disconnecting the Mac from the network and opening any of the files marked with the cloud icon. This will be the solution to the majority of the problems described on this thread: Indexing of file contents by Spotlight, Quicklook and letting backup programs do their work on the local OneDrive folder.
Feb 11 2022 11:53 PM
If I delete a folder from the OneDrive web, the local client first removes everything from the local machine and moves it to the bin (which is fine)... and then reuploads a couple of randomly selected files and folders back to OneDrive, creating some of the deleted folders and files again, i.e. goes against the latest change by re-uploading some random files back to the cloud. So one has to again delete files locally for the change to stick.
How exactly is this normal behaviour? This is so basic that it is incredible it wasn't adequately tested and caught early in development. Is this an alpha version? Windows Live Mesh worked better than that.
(More of a rhetorical question as issues raised in this thread are apparently not addressed, there are only Qs here and not many As. Not that I care particularly anymore, as after using and loving OneDrive for years and tinkering with it for the past two weeks in an attempt to make it work, I have finally simply downloaded everything off the web and moved to a different provider.)
Feb 14 2022 07:37 AM
Feb 14 2022 10:11 PM
@Ankita Kirti @Jack Nichols @gacarini @Carter_MSFT Where are you? Why have you all gone silent?
Feb 15 2022 12:29 AM
@Ankita Kirti Why is this thread titled QA? Where are the As?
Feb 15 2022 03:34 PM
Feb 16 2022 04:17 AM
Feb 16 2022 09:59 AM
Feb 16 2022 04:01 PM
Feb 16 2022 05:43 PM
Feb 17 2022 12:50 AM
Feb 18 2022 06:21 AM
Feb 18 2022 08:19 AM - edited Feb 18 2022 10:15 AM
@Ankita Kirti @Jack Nichols @gacarini @Carter_MSFT This nonsense has gone on too long. We need updates and solutions NOW. This can't wait another few days, weeks, months. Totally unacceptable, and frankly pretty sad from an organization of your size and virtually unlimited resources. When will all of the problems noted here be fixed? Provide a specific date.
Edit: cc'ing @Jason Moore too, Head of Product for OneDrive, since everyone else tagged here is useless.
Feb 18 2022 06:02 PM
@rvisima We did put a post on the main blog on Tuesday, 2/15
2.15.22 UPDATE: We're actively reviewing feedback and are aware of the difficulties some users are experiencing with the recent update. We working as quickly as possible to resolve these issues. We will share an update soon.
We will post another update next week, 2/23, with some resolutions and next steps.
Feb 18 2022 06:16 PM
@Carter_MSFT With respect: the "update" posted on 2022-02-15 was not posted as an addendum to the blog itself, but as a comment. Only a fraction of people who read any given blog read the comments, and certainly not out to 9 pages of them; those of us who were subscripted to the thread saw it. None of the thousands (if not millions) of other affected customers did.
Secondly, the comment was three days ago, said "we'll update something soon", and then there was nothing. "8 days later" is not generally considered "soon" when these issues have cost people priceless data and threatened the ability of some to remain employed.
Some of us work remotely enough there isn't and office to go in to for faster internet...and that's before you even take into consideration that some of us (such as myself) are COVID-vulnerable. What is the expectation here? Risk our lives to go somewhere full of people just to get enough internet to un[redacted] your [redacted]-up? With only a "hold your shorts" after _weeks_ of nothing, and then finding out days later that it will be at least another week for additional info?
Look, I work on a product management team myself. And I've done my time in product marketing as well. I honestly do get what the Onedrive team is going through right now, and how much the associated threads have almost certainly become a multi-tentacled box of nightmares for all the community staffs assigned to keep the box of cats from being too chaotic.
But, again, with all due respect, the customer communication regarding these issues has been bad enough to make a whole new textbook out of.
Please just tell us which of our concerns you intend to address, and give us rough timelines for them. If you, for example, are not going to resolve the "streaming files is the way we are going to do things and you will like it, the end" approach, then have the respect for your customers to tell us that, and tell us that right now. That at least allows us to go to our IT teams, present the problem, ask for solutions, and if we have to, start finding alternative employment.
Don't leave us hanging. That's a [redacted] move, bro.