Every time I have to update eM Client, I find my custom sound in Notifications has been changed. I don’t mean it’s reverted to the default – the actual .wav file is missing from the Contents>Resources>Sound folder, and I have to add it again each time. Then it’s fine until the next update. I’m assuming this is folders being overwritten rather than files within them being selected for deletion. I only have one notification sound set up (new mail) so while it’s frustrating, it’s not a long job, but I don’t know if other less noticeable settings are being changed in this way as well. If it’s in a feature that doesn’t get used often, then I might not have spotted one yet.
1 Like
Yes I also find my custom sound is gone from the folder after upgrading and have to put it back like my custom swoosh sending mail sound.
Be good if the devs could find a way to leave your custom sounds in the folder when upgrading.
It is a mac specific behaviour. I have made a ticket for it in our system and it will be resolved in a future version.
1 Like
Thank you.
You are not supposed to copy resources into the application bundle. The right place for custom sounds is ~/Library/Sounds. You can create the folder if it does not exist. Then your sounds will survive updates.
When you update or reinstall the application on Mac, the whole application bundle (eM Client.app) is deleted and replaced with the new version. No surprise that the resources vanish in this case.
2 Likes
Thank you! I actually did it that way when I first installed eM Client, but it defaulted, which is why I’d been adding the sound file within the app. I’ve tested it again today and now it works fine.
The right place for custom sounds is ~/Library/Sounds
I did have a ~/Library/Sounds folder but couldn’t access that folder from within eM Client when selecting the location even though i could access that via the Go Menu on the Mac.
So i ended up putting the custom sending and receiving sounds in my “iCloud/Documents/eM Client folder” and could access that fine from within eM Client and works fine.
I’m glad I wasn’t imagining it failing to pick up the file from within the app. (Although it obviously did today.) I await the next update with interest.
Yes, it’s unfortunate that it navigates you to the application bundle. It should be redesigned.
I did have a ~/Library/Sounds folder but couldn’t access that folder from within eM Client when selecting the location even though i could access that via the Go Menu on the Mac.
It’s interesting, because when the app lets you navigate to a folder and you confirm it by clicking Open or Choose button in the system OpenPanel, the OS grants, or at least should grant the application access to the selected folder.