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

macOS Catalina - Settings resetting after application restart #1423

Closed
scottrobertson opened this issue Aug 11, 2019 · 4 comments
Closed

macOS Catalina - Settings resetting after application restart #1423

scottrobertson opened this issue Aug 11, 2019 · 4 comments

Comments

@scottrobertson
Copy link

Hey

Running the latest macOS Catalina beta. With Mackup enabled, settings for apps such as Bartender, iTerm2, and others are resetting when i close the applications and open them again.

Used Mackup for years, and never had this issue.

I did have to move away from the icloud storage adapter to a normal file_system one because of #1386, and i placed the mackup files in my Documents folder so they would continue t sync

@lra
Copy link
Owner

lra commented Aug 25, 2019

So is it working again since you don't use iCloud?
Also Bartender might have some other issue per #1126

@icopp
Copy link
Contributor

icopp commented Sep 30, 2019

I tried the same thing with moving the Mackup folder into Documents. It looks like the problem here is the new limitations on folder access Apple put in place. See the Security & Privacy preference pane and the Full Disk Access and Files and Folders settings. If you add a misbehaving app to 'Full Disk Access' it should then work as expected.

I'm guessing this is related to some use of specific APIs, because I've seen some apps automatically trigger the 'X would like to access the Documents folder' popup, while others just die ignominiously instead or fail to recognize they can't save files.

@tshu-w
Copy link

tshu-w commented Oct 12, 2019

Same issue here. Some apps don't work well with Full Disk Access, eg. iterm2, Dash, etc. And this also happing in the system setting.

@jasongregori
Copy link

Thanks for this. I think this finally explains what's happening. I guess certain apps must be directly writing to their preferences and dont have permission to access where the symlink actually goes. I definitely hit this a ton with only some apps.

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

5 participants