Download
Auto-updates: In progress
Thanks for using Dropbox! Here are the user-visible changes in v89:
Does this fix the perpetual "Syncing..." problem with version 88.4.172?
Does this fix a bug with files >2GB not syncing (in either direction) on 32-bit Linux?
@bobas wrote: ...Linux 32-bit releases are now cross-compiled on 64-bit Linux
...
Hi @bobas,
What actually this mean?! 32-bit builds was always possible to be used in 64-bit environment. What is the new thing here? :thinking: Aah... You have just discovered that's possible. Congratulations! :slight_smile:
The 64-bit build still has issues opening submenus!
@PlsFixSyncing wrote: Does this fix the perpetual "Syncing..." problem with version 88.4.172?
Since the sync delay is due to what appears to be a TOTAL REINDEX for a new SQL engine you can expect its going to be in this version as well, even if they reversed the SQL engine back to the old method, then that one woiuld have to reindex as well so your still stuck.
Im as FRACKED OFF as can be, it takes days / weeks for a reindex to complete on our data as we have 2TB+ in 600K+ files.
Any educated developers would know to migrate the database, but DB , Oh no lets just do a rebuild, who gives a stuff if it doesnt sync for days I mean our customers can lump it we are the gods of self amazement and the light shining from us well show the way.
Priase the D & the B for all sync shall come to those who wait for the weeks of reindex to pass, and the stale data shall be theirs for the taking.... SHOOT ME NOW!
still endlessly 'Syncing...', still thrashing the drive at 100%. Zero indication of what's actually happening. This is pathetic.
@Graeme T.1 wrote: Does this fix a bug with files >2GB not syncing (in either direction) on 32-bit Linux?
No, I can say it doesn't. I have a ticket opened with Support (for the previous version v88.4.172), and I've updated it to say that this version hasn't fixed the issue either.
Installing version 89.4.278 has not solved the "Syncing..." problem on Windows 10.
EDIT 2 Feb 2020: Uninstalling Boxifier solved my syncing issue. (It's not enough to exit Boxifier.)
This notice is about how we create builds when releasing them, not about running them.
Previously, we would use a 32-bit machine to compile the 32-bit Dropbox application.
Now we use a 64-bit machine to compile the 32-bit Dropbox application.
There should be no regressions in functionality due to this, but, since the overall population of 32-bit users is small, we are unable to test every feature. This is a heads up so that users can tell us if they notice any problems.
Here is some more information about cross-compiling - https://stackoverflow.com/questions/897289/what-is-cross-compilation.
Customers don't care how you compile your code or app. Customers pay you for features or services which you provide. It doesn't matter 32-bit or 64-bit they are using.
Hire more QA engineer or take away the 32-bit at all. Otherwise provide quality product.
"This notice is about how we create builds when releasing them, not about running them." - you should run them and test before you upload it on the production server. Or correct or return to the backup quickly. And what do we see "Installing version 89.4.278 has not solved the "Syncing..." problem"....
"we are unable to test every feature", "users can tell us if they notice any problems" - I hope you are not developing software for cars.
@nikhilm wrote: This notice is about how we create builds when releasing them, not about running them.Previously, we would use a 32-bit machine to compile the 32-bit Dropbox application.Now we use a 64-bit machine to compile the 32-bit Dropbox application.There should be no regressions in functionality due to this, but, since the overall population of 32-bit users is small, we are unable to test every feature. This is a heads up so that users can tell us if they notice any problems.Here is some more information about cross-compiling - https://stackoverflow.com/questions/897289/what-is-cross-compilation.
This explains why I'm having problems with 32-bit machines - you're not testing it on a 32-bit machine with files larger than 2GB so you don't see problems. I suspect it's linked to the maximum signed integer size on a 32-bit machine (2^31-1: https://en.wikipedia.org/wiki/2,147,483,647), and 2GB is one byte more than that.
I'm still experiencing the endless sync problem that everyone else started having from the update 2 weeks ago and discussed here: https://www.dropboxforum.com/t5/Files-folders/Dropbox-is-stuck-syncing-after-an-update-what-can-I-do/m-p/392086
Hi @nikhilm,
I fully agree with @Hexrby! "Customers don't care how you compile your code or app. Customers pay you for features or services which you provide." Customers interest in working solutions and quality products! Yes, more QA is need, for everything. No for misbehaving (buggy) databases, which needs "refresh" (i.e. reindexing everything), from time to time, not very clear why exactly every time. That's the really important!
About cross-compilation: Are you count just adding one option '-m32' as a big and heavy new feature?! Seriously?! You don't have to change even the compiler! If you want to introduce new feature, try provide real cross-compilation for ARM architecture, for example. Something many customers would appreciate! If you want to know something more about cross-compilation, especially in Linux, take a look. The last, but not least, what kind of such compilation we are talking about, while the main application part is in Python (i.e. scripting language, which compile to platform indipendent bytecode) - only for few libraries?!
Good news is your "new feature" don't affect how menu appear of the 32-bit version (i.e. works, still). Unfortunately, the same statement isn't true for 64-bit build, still! For example, in 32-bit build every submenu looks like:
Same thing on 64-bit build looks like:
As could be seen, no any trace to any submenu (either changes or snooze).
Something else: while hover Dropbox systray icon the popups are different. For 32-bit build everything looks fine:
There is information what's going on. For 64-bit build such info is missing:
There is something wrong in your 64-bit build, as could be seen above.
There is also something wrong for both, 32 and 64 bit builds. File browser views stay inupdated after sync finished:
Please, Fix everything noted above!
Hi, Since Thursday, I have been having issues with the Preview App on macOS Catalina:
Everytime I open a PDF or document, the Preview App beach ball with the document being blurry for 2 seconds, then it opens fine.
After several tests (reset NRAM, caches, Onyx cleaning, Safe Mode, font cleaning, etc) I found the following:
Drag the file out of my Dropbox folder, and no issue whatsoever!
Drag it back in the dropbox folder, and here we go again, beach ball freeze when the preview App opens.
So there is definitely something up with Dropbox.
I also get this message in the console upon opening a file in Preview and beach balling:
Jan 24 15:36:26 MBP-16-JU com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.4xxxxxxxxx[1609]): Caller wanted oneshot behavior for pre-existing instance: caller = Preview
Problems started exxactly when last build of dropbox has been installed.
Regards,
@Julien6767 wrote: Hi, Since Thursday, I have been having issues with the Preview App on macOS Catalina:Everytime I open a PDF or document, the Preview App beach ball with the document being blurry for 2 seconds, then it opens fine.After several tests (reset NRAM, caches, Onyx cleaning, Safe Mode, font cleaning, etc) I found the following:Drag the file out of my Dropbox folder, and no issue whatsoever!Drag it back in the dropbox folder, and here we go again, beach ball freeze when the preview App opens.So there is definitely something up with Dropbox.I also get this message in the console upon opening a file in Preview and beach balling:Jan 24 15:36:26 MBP-16-JU com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.4xxxxxxxxx[1609]): Caller wanted oneshot behavior for pre-existing instance: caller = PreviewProblems started exxactly when last build of dropbox has been installed. Regards,
Same problem here, but dragging files out of Dropbox doesn't fix anything. Yet, for me the issue also started yesterday, i.e. with the latest version of Dropbox.
See also this thread:
https://forums.macrumors.com/threads/annoying-freeze-and-spinning-wheel-in-preview-catalina.2220788/
I am also still experiencing endless un-numbered synching problems on my Win10 machine. This is pathetic.
Ronald -- please check my solution to the un-numbered syncing I posted here: (my long post outlining symptoms and solutions): https://www.dropboxforum.com/t5/Files-folders/Dropbox-is-stuck-syncing-after-an-update-what-can-I-do/td-p/389422/page/12
Is there a way to revert to build 88.4.172 and at the same time prevent auto-update? This Preview problem on MacOS X Catalina is really annoying as I work with PDF files all the time (I am a researcher), it also interferes with LaTeX!
Thanks.
Hi @fcorm,
Take a look here.
Hope this can help you.
@ЗдравкоThanks a lot, works like a charm!
@ЗдравкоThank you for this! :-) Quick question, where do you find the "Download earlier version of your choice"?
And also, to do what is mentioned in your link, do you need to uninstall the current version of dropbox install, and will it be able to overwrite it with the new earlier version of my choice?
Hi @Julien6767,
Download earlier version of your choice.
It's not mandatory to uninstall your current version, if not need for some other reason. Selected Install will override current install. Read more carefully for the unfreezing.
Hope this adds clarity.
Hi @tonyskate,
Absolutely same - no, but equivalent - Yes. When you want, removing Deny mark will let Dropbox auto update again. You didn't mention explicitly and I assume you ask for revert to previous version. Alternative variants are also possible in all cases (just preventing updater process run, in cases there is such independent process - on Windows & Mac there is).
Hope this helps.
Hi @Здравко, thanks but that did not help. Dropbox tries to update anyway and when I stop the process before it's done, Dropbox in older version is still stuck at syncing and eats CPU & disc.
It has been like that for about two weeks and Dropbox support does not care at all or more propably they don't have any solution and who knows if they are gonna ever fix it.
Probably you didn't notice:
@Здравко wrote: ... You didn't mention explicitly and I assume you ask for revert to previous version. ...
... You didn't mention explicitly and I assume you ask for revert to previous version. ...
I'm commenting how you can revert Dropbox version, nothing more. I don't use Windows regularly, in fact, to be honest. I fully agree that Dropbox QA is very bad and need significant improvements, definitely. They use final users as some alpha testers (and all this for "stable builds")!
No worries, @Здравко. Yes, I have wanted to revert Dropbox version but it didn't work. It was worth a try, thank you anyway.
