Ross_S Dropboxer

Comments

  • Hey folks, Sorry for the delay in getting back to you, but we have great news! We have a build here of the desktop application that we believe should fix this issue: https://www.dropboxforum.com/t5/Dropbox-desktop-client-builds/Beta-Build-167-3-4684/td-p/654175 Hope this helps! Ross S.
  • Hi @"sinus" , I'll reach out to you via email and see if we can help! Many thanks!
  • And I'm back... Yes, due to a technical issue the emails were incorrectly sent. There are 2 near-quota programs that should only email users +90% of quota, ​​it seems since probably around yesterday, that its been running incorrectly and doubled the amount of used bytes... so users that are 40-50% of quota are appearing as…
  • Hi everyone, I'm one of the Product Operations Managers here at Dropbox, and I'll jump straight on this. It certainly sounds like something's not quite right. We're investigating to make sure we have the threshold correct, normally atleast 80% of your Dropbox space needs to be used before you'd get an email like that.…
  • Hi there, Yes, this looks expected, we call that when we uninstall the DropboxOEM. You'll only see this on Windows 10 as it related to the UWP version of our app. Via Powershell we're uninstalling the DropboxOEM from system level so that it does not get installed again. This effectively cancels scheduled installation of…
  • Hi folks, I have good news here, we have a fix for this, it's in our v59 beta: https://www.dropboxforum.com/t5/Beta-testers/ct-p/101003000 The fix will also be included in our upcoming v59 stable, which users will auto-update to around the 10th Oct all being well. Hope this helps!
  • Hi all, We have pushed a server-side fix. You should see that the Doc Scanner now functions as expected. There's no need to update to a new build, as the fix exists on our server. Many thanks for your patience!
  • Thanks all for reporting this problem. We detected it ourselves and have been working on it in the background, but I wanted to update here too. I can’t say exactly how long this will take to resolve, however, we believe we are making good progress and I hope to update here soon that we have a fix ready for this.…
  • Both.... and you already have it! We added the code a while ago, then have been slowly ramping it up with server-side gating. It has now reached 100%, so code already in the build is now live to everyone.
  • Hi everyone, I wanted to give you an update on the issue of mdworker crashing when reading a mismatch in the expected logical vs physical size of PDFs on Mac. Firstly we've not forgotten about this, a lot of work has been going on in the background to resolve the issue. It has required extensive code re-writing. For those…
  • Issue with long filepaths or counting the contents of a container file maybe? Doesn't sound like it's being caused by a reparse point, I don't think. Are there any filenames over 260 char? something like: dir /s /b | sort /r /+261 > out.txt would probably check for that. There may be better command lines available to check…
  • I wonder if we have a misunderstanding of what the button does: Open -> Open in Microsoft Word = Open the actual Word doc that I already have on my desktop If the doc isn't there then it will not open. If you can't see the doc in that folder then I wouldn't expect to see that functionality. Unless I missed it, can you…
  • I'd also suggest ensuring you have no folders selectivley synced out, as that could account for the discrepency. As an advanced suggestion: It may be worth using the command prompt to check the size/contents ofthe folder too, rather than the traditional Properties view. maybe doing something like: dir /s…
  • Hi folks, I wanted to jump in again as my other posts are getting lost in the thread. This is something we are aware of, it's also something we are working very hard on internally to resolve. Navigating this particular OS behavior is not a simple, quick fix. We've been working on it for some time due to the complexities…
  • I hate to suggest it, but.... Have you tried restarting? ... I know that can be the worst "advice" to hear, however I think it's very possible that some part of the install process didn't completly disengage - for want of a better word - and this could be impeeding the uninstall. The Advanced Reinstall instructions above…
  • Hey folks, The Open button allows you to either open the file locally, or via Office 365. If you are not seeing the option to open locally it's because the file isn't present on that machine. Can you ensure that Dropbox is running firstly, however the most likley issue here would be that you may have Selectivly Synced out…
  • Ah, the change we made to leverage sparse files introduced in APFS hasn't landed in the public facing build yet. Sorry about my over-eagerness there. The change will make it into the stable build in due course, we just need to complete testing on it. I'll post an update once it does, so, at this point, let me just correct…
  • Actually mdworker crashing is due to the way apple interacts with certain filetypes. The issue is only present on HFS file systems, so, with the introduction of spares files on High Sierra - which uses APFS - this issue is resolved. For context, firstly, while you see the errors within event log there are no issues with…
  • Hi all, We are currently working on this issue and I hope to bring you a concrete update soon. At this point all I'm able to share is simply that we're activley persuing a solution here. I'll update more when I have a timeline on the fix. Many thanks for highlighting here!
  • Hi all, Thank's for flagging that this isn't fixed for all, we'll loop back to Trend Micro and discuss it further with them. Can those still hitting the issue confirm that they are running Trend Micro Worry Free Business - and have our Smart Sync? I'll update here again once we have more to share. Many thanks.
  • Many thanks for highlighting everyone! The fix for this will be in v101 of the app. Please ensure you continue to update to the latest versions.
  • Thanks @"Jay" + @"Lancelot". We did end up getting to the bottom of this. This isn't a "bug", but a change in behaviour that only happens in certain circumstances. My guess here is that you have a graphics tablet or 3rd party mouse connected perhaps @"Lancelot"? As this is designed behaviour by Apple, it's not something…
  • Hi folks, I just wanted to post here to acknowledge that we are looking into a possible conflict with Trend Micro. I'll reach out to a few of you via email with extra debugging steps. Many thanks for spotting the issue!
  • I've reached out to you both individually via email as my team have different questions for each of you. Many thanks, and we are activley investing this for you.
  • Hi there, Appologies, on review I'm now looking down a different avenue. I'll speak to the engineers and see what we can diagnose here. Many thanks for highlighting.
  • Hi folks, We had an 2 issue previously, one where the user set preference wasn't being adhered to, another where we ran an experiment changing the behaviour. That's what I was referring to above. I'm checking incase either of these are currently impacting Linux, but I don't believe so, we resolved one and changed the…
  • Hey @"Rich", You will see improved preview (using a monospace font and adding support for speed scrolling) and introducing text editing for the first time for these filetypes: ADA, ADS, AHK, APPLESCRIPT, AS, ASM, AU3, BAS, BAT, BB, BMX, C, CFG, CLJ, CLJS, CLS, CMD, COB, COFFEE, CPP, CS, D, DBA, E, EFS, EGG, EGT, EGT, EL,…
  • Hi there, they should use minimal resources. Amongst the processes you'll see: - One, the one using decent resources, is our application. - We'll run a updater process, it's separate and will ensure, if a critical issue occurs we can separately update the app back into a working state. It'll also independently pull down…
  • @"majomabaja" we'll reach out to you right now!
  • Sorry it's taken me so long to get back. We should now have resolved the issue where, when some opt into Smart Sync, you proceed to grant Accessability but can't proceed. Is anyone still hitting this on macOS 10.13+ ? Many thanks!