SketchUp 2020 always thinks there is a newer recovered file.

ValmontR

Lately every time I open a file I get a dialog:

"The recovered version of this file is newer than the file.
Open the recovered version instead?"

The two problems are:

It is not a newer version
Even saving the file does not clear this warning the next time I open a file.

The bug is nothing fatal but it is getting annoying.

Cheers,
Ralph

iMac - Retina 5K, 27-inch, 2019
3.6 GHz Intel Core i9
2 GB 2667 MHz DDR4
Radeon Pro Vega 48 8 GB

OS 10.14.6
SketchUp 20.0.362

markchandler

Is the folder where you're saving the original model being backed up by iCloud by any chance?

sfto1

I'm experiencing the same issue.

As far as I know, I'm not saving to the cloud. I'm saving either to my local machine or to the network server.

pbacot

Find the Recovered Files folder. I think it in SketchUp /Application Support, I put it in the sidebar so I can throw out the contents regularly.

markchandler

Recovered (aka, auto-save) files are located here:

/Users/YourUserName/Library/Application Support/SketchUp 2020/working/SKETCHUP/RecoveredFiles/

db11

My experience has been that this happens when you have some type of abnormal SU exit: a bugsplat or freeze.

There seems to be some code that executes on normal exit that does the proper comparison and if it doesn't complete, then it thinks the recovered file is newer than the actual current one — and will (incorrectly) prompt you every time you open that file until you trash the recovered file from the location described above.

This is clearly a bug that has been brought up over on the official SU forum, and it's not limited to SU 2020. I first experienced it with SU 2019.

Hopefully the bug is logged and it will be fixed eventually — it becomes especially confusing when you have a couple of crashes in a row to determine which is the file you should be opening vs. trashing.

markchandler

We've reproduced this with 2019 and 2020 and are opening a bug.

laterstarter

Thanks for raising this issue as It happens to me as well. Always thought it was a problem with my workflow. Thanks Scott

sfto1

@markchandler said:

We've reproduced this with 2019 and 2020 and are opening a bug.

Thank you for looking into this. It's caused me some grief