[macOS] "The user name or passphrase you entered is not correct." due to App Translocation after updating

[gingerbeardman]

The problem

Recently (the past 2 versions) when the app updates itself and I restart it, I am no longer logged in.

The app seems to be under translocation/gatekeeper protection and it's quite a hassle to get it to work properly.

Login works, but ability to push remains broken. Restarting repeats the process

Release version

3.1.2

Operating system

macOS 12.6.1

Steps to reproduce the behavior

1. use macOS
2. let app auto-update
3. restart app

Log files

2022-10-25.desktop.production.log

Screenshots

Additional context

To workaround the issue:

1. move the app somewhere out of Applications (I chose Documents)
2. zip the app using macOS Finder built in compress menu item
3. delete the original app
4. unzip the zip to get the app back
5. move the app to Applications folder
6. delete zip if it's still there

[steveward]

@gingerbeardman thanks for the report. Previously when we've seen the The user name or passphrase you entered is not correct' error locking and unlocking the loginkeychain inKeychain Access.app` has resolved it. Have you tried that to see if it resolves the issue?

[gingerbeardman]

Curious!

However, my login keychain is already unlocked. So, no, it does not resolve the issue for me.

I have the zip & unzip workaround, but I'm wondering why it's needed.

It would be great if the Desktop could detect it was running under App Translocation and... do or prompt something?

[gingerbeardman]

Just had this again updating in-app from 3.1.2 to 3.1.5 on macOS 12.6.3

My workaround this time was different: simply download latest through the website and install manually through unzip, mount, drag-and-drop, open.

Bizarre that installing through the in-app update ends up with the app being in App Translocation purgatory.

[gingerbeardman]

Happened again with the most recent update 3.2.1

Can't remember if I was upgraded to any interim releases.

• 3.2.0
• 3.1.8
• 3.1.7
• 3.1.6

[gingerbeardman]

And again with 3.2.3

[gingerbeardman]

Still happening

• 3.2.6

[gingerbeardman]

happened again with

• 3.2.9

[gingerbeardman]

3.3.1 OK

[gingerbeardman]

3.3.3 OK

[gingerbeardman]

3.3.4 OK