4.3.1 Corrupt list data work around

There is an issue with the migration process from 4.2 to 4.3.1 if you have relative date smart lists. On the second run of 4.3.1, BaseCamp will prompt that your list data is corrupted and it will revert to your backup (4.2.4) data. The only operational problem (other than the annoying prompt) is that any new list data is lost.

To work around this issue, delete and recreate any "date" smart lists using BaseCamp 4.3.1. There are many new options to date smart lists options that you can take advantage of. Any changes you make from that point on will be saved and the prompt will go away.

We are working on releasing 4.3.2 with the issue fixed as fast as we can, but the process typically takes a week. Making the software change is the easy part, but in the meantime the workaround should allow you to use 4.3.1 going forward without issues.

0 Former Member over 11 years ago

I have no problem with the update, but I did remove the 4.3.x beta release database from my personal library before starting BaseCamp 4.3.1:

~/Library/Application Support/Garmin/BaseCamp/Database/4.3

Even a next time starting up is no problem.

0 PSEABOLT over 11 years ago

I have no "date" smart list so I installed on three Mac's. First time installing on each computer erased BC 4.3.0.1 but did not install 4.3.1. Had to run the installer a second time to get BC 4.3.1 installed. OS 10.9.3 Mavericks

0 Halt001 over 11 years ago

I'm currently fighting to get the very very very buggy Edge 1000 to work and in the mean time you manage to throw away my complete data organisation. Way to go Garmin. Im getting a very warm feeling right now.:mad:

0 Killtimer_ over 11 years ago

I have no "date" smart list so I installed on three Mac's. First time installing on each computer erased BC 4.3.0.1 but did not install 4.3.1. Had to run the installer a second time to get BC 4.3.1 installed. OS 10.9.3 Mavericks

I had the exact same issue.

0 BUNKERBUSTER1273 over 11 years ago

You can try to recover your old "list" deleting a folder....
Bunker

0 azdrmn over 11 years ago

Most people shouldn't have to delete any files for this workaround to work. If you got the message that your list data was corrupt, but loaded the backup, then you haven't lost anything from 4.2.4. If it said both are corrupted and all your folders were gone then you might have to delete ~/Library/Application Data/Garmin/BaseCamp/Database/4.3, then do the workaround of deleting all relative date smart lists. Again sorry for the inconvenience.

0 Former Member over 11 years ago

I think I'll stick with v4.2.4 until this is fixed; I can no longer afford to risk my data.

When I give my class on v4.3 at the BMW MOA Rally in July I hope this has been dealt with appropriately.

Maybe Garmin would like to attend the Rally since the majority of the 3000+ attendees use Garmin products.

0 Former Member over 11 years ago

Unacceptable, this has cost me half a day. Someone should be fired.

0 Former Member over 11 years ago

Most people shouldn't have to delete any files for this workaround to work. If you got the message that your list data was corrupt, but loaded the backup, then you haven't lost anything from 4.2.4. If it said both are corrupted and all your folders were gone then you might have to delete ~/Library/Application Data/Garmin/BaseCamp/Database/4.3, then do the workaround of deleting all relative date smart lists. Again sorry for the inconvenience.

This workaround assumes that "most" Mac customers don't use SmartLists. But, if the customer does and if they installed v4.3.1 over v4.2 (the normal update process), the customer is out of luck at recovering their FolderData until v4.3.2 comes out. Is that correct?

I suppose the customer could recover v4.2.4 using Time Machine assuming they know how.

0 azdrmn over 11 years ago

If you don't have smart lists, date relative smart lists in particular, then you didn't have the folder data issue with 4.3.1. So the workaround is only required by users with smart lists.