
Mailmate and TextExpander, apparent conflict
Reported by szoubok | March 3rd, 2025 @ 02:49 PM
Good morning!
Over the past couple of weeks there seems to be a conflict between Mailmate Version 1.14 (5937) and TextExpander 8.2.2.
I have noticed this on three Macs (M1 Mac mini, M2 Mac mini Pro, M1 MacBook Air), all running Sequoia 15.3.1.
On all the machines, Mailmate occasionally hangs with the "spinning wheel of death" until I force quit TextExpander, at which point Mailmate starts loading mail and working normally. I can then relaunch TextExpander and all is well, at least for a while. The problem is sporadic but happens at least once every couple of days.
I'm reporting this to the TextExpander team as well.
Thanks,
Sergej
Comments and changes to this ticket
-
benny March 3rd, 2025 @ 03:01 PM
Hmm, this might be related to some other recent reports (past 4-5 days). These reports indicate that MailMate gets into trouble every time it has to update the access token for an OAuth2-enabled account which might match the sporadic behavior you are seeing. I don't really see how it's related, but maybe.
In any case, use Activity Monitor to sample the process when it's hanging and send it to me using Help > Send Feedback.
...
Ok, this already seems to be confirmed by at least one of the users with this problem. I'll look into it in more detail when I have time.
-
-
Matthew March 3rd, 2025 @ 08:57 PM
Just chiming in that I'm experiencing the same issue - and killing Textexpander does the trick with resolving it for now.
Also on Sequoia and using Mailmate v2 (6222).
-
benny March 4th, 2025 @ 11:11 AM
I've added a quick workaround to the latest test release of MailMate. It'll allow you to enable that MailMate caches tokens in-memory without trying to store them in Keychain Access. This means MailMate will get a new access token whenever MailMate is relaunched (which is fine), but IF a new refresh token is needed (typically for new accounts) then it also means that authentication (via the browser) will be required on every relaunch.
defaults write com.freron.MailMate MmOAuth2TokenCacheEnabled -bool YES
Hold down ⌥ when clicking “Check Now” in the Software Update settings pane to get the latest test release (r6234+).
-
Sebastian Hagedorn March 4th, 2025 @ 11:25 AM
FWIW: I don't use TextExpander, but I do use Keyboard Maestro, which is very similar. I've also noticed hangs: sometimes my keyboard shortcuts don't work. I found that their operations only happen after I have switched to a different application and then back to MailMate. I cannot say for certain these symptoms are connected to Keyboard Maestro. I usually quit and reopen MailMate when it's in such a state.
-
benny March 4th, 2025 @ 11:30 AM
@Sebastian: Unlikely to be related to the hang/crash, but let me know if you figure out a way to trigger this issue.
-
benny March 4th, 2025 @ 04:51 PM
NOTE: The r6235 release has a bug which has been fixed in r6236 linked further below.
The following download uses a different API to store tokens in the keychain: https://updates.mailmate-app.com/archives/MailMate_r6235.tbz
I'm interested in knowing if it works without the cache trick described above (with TextExpander running):
defaults delete com.freron.MailMate MmOAuth2TokenCacheEnabled
(There might be other issues. This was a quick rewrite of the related code. There's more to do and the same problem likely exists for regular passwords, but these are stored less often.)
-
Matt Johnson March 4th, 2025 @ 06:35 PM
Just adding another +1 to this issue... thanks to Sergej for figuring out that it was TextExpander because this was driving me nuts. I also have TextExpander 8.2.2, was recently running the normal release of MailMate which I believe was build 5937, but just switched to the beta (6222) as part of the debugging process. FWIW, I'm still back on Sonoma 14.4.1.
For now, I'll just quit TextExpander when running MailMate but will try to keep an eye on this thread and try/test/report back on subsequent builds with fixes when I have time. Thanks, Benny!
-
Alex Nonnemacher March 4th, 2025 @ 11:51 PM
I updated the test build that Benny recommended, added the terminal command, and launched both apps. Seems to be working now.
-
Kevin McAllister March 4th, 2025 @ 11:55 PM
This may not be helpful but wanted to add my wife uses Outlook for work and recently updated to 15.3.1 and she was having trouble sending email. Basically she'd try and send and the email would leave her drafts, would not go into sent, and the client would no longer work. It wasn't until Benny pointed this out to me that I told her to quit TextExpander when it happened and Outlook started working again.
I'm going to report to TextExpander too.
-
benny March 5th, 2025 @ 03:11 PM
The release linked above has an issue with saving tokens. I've fixed that and I've also switched password store/restore to use (mostly) the same code. I'm no longer using any obsolete Apple APIs to do this. It might not fix the issue, but this change was needed in any case.
Please try this one: https://updates.mailmate-app.com/archives/MailMate_r6236.tbz
Also please disable the temporary workaround described above (which still works):
defaults delete com.freron.MailMate MmOAuth2TokenCacheEnabled
I'd like to know if the new code has the same issue as the old code.
(There is, of course, also the possibility of new bugs in the new code.)
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Mac OS X email client.