Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update resets columns #376

Open
ghost opened this issue Sep 3, 2023 · 4 comments
Open

Update resets columns #376

ghost opened this issue Sep 3, 2023 · 4 comments
Assignees

Comments

@ghost
Copy link

ghost commented Sep 3, 2023

Whenever there's an update to Cog, downloading and installing the update from within Cog resets my column settings to the default.

Example: Before the update:

Screen Shot 2023-09-03 at 8 53 52 AM

After the update (just now):

Screen Shot 2023-09-03 at 8 54 27 AM

Please make Cog stop doing that. Thank you!

@ghost ghost assigned kode54 and nevack Sep 3, 2023
@kode54
Copy link
Collaborator

kode54 commented Sep 3, 2023

This seems to be a bug with the UserDefaults container that is used to store these settings. I have no idea why it's doing it, either. It doesn't seem to do it on any more recent macOS versions, either. Anything Big Sur or newer doesn't seem to be affected.

Apple is also making it harder to debug this, by removing Rosetta debugging from Xcode.

@ghost
Copy link
Author

ghost commented Sep 3, 2023

Agreed, I should have mentioned that this is High Sierra. Let me know if I can do more to help debug, such as looking in the prefs file.

@kode54
Copy link
Collaborator

kode54 commented Oct 9, 2023

I don't know that it's the prefs file at all. The issue seems to happen on anything older than Big Sur (11.0), and I don't know how long it's been going on.

@ghost
Copy link
Author

ghost commented Dec 10, 2023

It seems that this might have something to do with restarting the computer. I was using Cog just fine, but then because of a schedule power outage I shut down the computer. When the power outage was over and I started up the computer again, Cog had reset its columns to the defaults. So it seems as if Cog is not writing out the column settings to persistent storage in a way that it can use to reconstruct them when relaunched from a cold start. Sorry, I know I'm just hand-waving, but I'm trying to give as much info as I can, when I encounter it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants