GPGMail - Beta Expired, new version downloaded but would not activate
I had the 'beta expired' message but could still go to mail preferences and click 'check now' for the new beta and download it. After installing the new beta, mail restarted and I received the same 'beta expired' message and GPGMail was not available. I had to download and install the bundle from the website to recover GPGMail. As a side note, the upgrade process for GPG Keychain Access worked flawlessly :)
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Steve on 31 Dec, 2014 03:40 PM
Hi Robert,
we've reveice some reports where a second re-installation of GPG Suite Beta 4 did the trick, while the first installation still did trigger the "expiry" message.
Could you try that?
All the best,
steve
2 Posted by Robert Goldsmit... on 01 Jan, 2015 01:33 AM
Hello,
Installation by downloading the bundle from the website worked fine. It was just the update within Mail that failed. To summarise the experienced behaviour:
1) I received the expiry message regarding beta 3 (correctly)
2) I selected 'check now' for the software update from the Mail preference pane and the download and install appeared to be successful
3) Mail was terminated as part of the install and so I restarted it
4) I received the expiry message again (incorrectly) and the plugin was not available to me
5) I downloaded and installed the bundle from the website and all is now back to working.
Robert
3 Posted by steve.mumford on 01 Jan, 2015 12:09 PM
Hi there - I had auto-updates selected in Mail - here are my experiences:
1) Auto-update triggers within Mail, but install didn't seem to complete (Mail didn't quit)
2) I trigger the update manually within Mail preferences, and Mail restarts; still get the expiry message
3) I installed the bundle from the website; still get the expiry message
4) I installed the bundle from the website for a second time; this time it seems to have worked
4 Posted by Richard on 01 Jan, 2015 03:13 PM
I've experienced the same behaviour. Reinstalling the package solved it till the next update....
Support Staff 5 Posted by Steve on 01 Jan, 2015 10:44 PM
Hi all, thanks for the feedback.
We've learned that some people have problems with automated updates. We're still investigating. The workaround is to simply install the newest version from our website.
Steve closed this discussion on 02 May, 2015 06:45 PM.