"Invalid Key Material Type" error in Beyond Compare 5

Hi there Tanker001 - thanks for bringing this to our attention.

I'm not entirely sure that this is caused by Dropbox, but let me run it by the team and get back to you.

Let me know if you have anything else to add or ask in the meantime. 

Sorry to say, but I have exactly the same problem...

Please help me out.

Hello all. Thanks for the detailed rundown, that was really helpful context into this.

This error appears to be coming from Beyond Compare’s connection to Dropbox, not from Dropbox itself. Your files are safe and should still be accessible on dropbox.com or through the official Dropbox app. You may have some luck by removing and reconnecting Beyond Compare as a linked app in your Dropbox account.

I tried deleting my Profile in BC5 so that I can recreate it.  Now when it launches the browser to obtain an authorization code I get the following error:

Has Dropbox changed the authentication process?  I ask because I now have to log in everyday, when I used to keep tabs open in my browser to the folders I access on a regular basis.  This seems to started about the same time as this issue with BC5.  Checking the "Remember me" seems to not have an impact.  If the authentication process has changed, have you communicated this to those outside Dropbox that build tools (like BC5) that access access a users data on Dropbox???

To be honest, I've never liked the Dropbox App.  I've tried it on at least a couple occasions over the past 8+ years (since ~2017) and have promptly uninstalled it.  I like the method that BC5 uses better and I also use it for scripting, comparing spreadsheets, and more.  I recently retired from boeing and I was an application/server admin and used BC5 on an almost daily basis.

Tanker001 wrote:

Has Dropbox changed the authentication process?

I don't think anything in the authentication process itself has changed, but the API servers have been updated with certificates from a new root. Any app using an SDK with the old certificates needs to be updated to a newer SDK version.

If Scooter Software hasn't updated Beyond Compare, it could cause the issue you're seeing. You should reach out to them directly for support with this.

Tanker001 wrote:

... have you communicated this to those outside Dropbox that build tools (like BC5) that access access a users data on Dropbox???

Yes, beginning 18 months ago.

• https://dropbox.tech/developers/api-server-certificate-changes

Rich gave the right answer

Dropbox hasn’t removed support for third party access, but authentication and security handling does change over time. The error you’re seeing happens during Beyond Compare’s authorization step, and your files are still safe. Since Beyond Compare manages its own Dropbox integration, the next step is usually to troubleshoot the OAuth flow with their team.

Thanks, guys.  Someone posted something similar on the Scooter software forum.  I'm just a user trying to figure out why I keep getting an error when trying to access my account through BC5.

I have noticed that something has changed with logging in via a browser.  My login now "expires" requiring repeated logins. 🤦‍♂️

FYI, I've never doubted the existence of my data.

Just an update for anyone who reads or is following this posting ... Beyond Compare v2.0 BETA has fixed this problem.  The official release is not available yet ... but you can test the beta and verify it is fixed when working with your implementation:  https://www.scootersoftware.com/beta

Thanks robinsoft​.  I tested the beta version in a Linux live session and found it did correct the issue.  I'm just making due until the version is formally released to start working with my live data.  The people at Scooter may have fell into the Dilbert zone and went through an "aw crap, I thought you did it" moment. 🤣