EagleFiler 1.9.21b1 Public Beta

EagleFiler
1

Here’s a new beta version of EagleFiler. The changes are:

  • EagleFiler is compatible with beta versions of the forthcoming macOS 27 Golden Gate. Please let us know if you encounter any issues. When launching EagleFiler, macOS may show a “Support Ending for Intel-based Apps” notification. This will be relevant for macOS 28 in fall 2027, and we expect to have an update available before then.
  • The capture key now works with MailMaven and will preserve e-mail message metadata such as the keywords, project, flag, importance, and notes, and also includes a link back to the original message in MailMaven (requires MailMaven 1.2, currently in beta, or later). For more information, see the Importing Mail From MailMaven section of the manual.
  • Importing from Mariner Paperless is better at handling errors; it no longer times out reporting them and now lets you skip over any files that are missing. It also now works with databases from the older version 2.x of Paperless.
  • Capturing from Outlook works better with very large selections of messages.
  • The capture key now works with the Helium Web browser.
  • Encrypted libraries now always use the APFS file system. Apple has announced that volumes using the encrypted Mac OS Extended file system will not be compatible with macOS 28 (in fall 2027). You can convert old encrypted libraries to the new format by rebuilding them or simply by creating a new encrypted library, closing both libraries, and using Finder to replace the contents of the new encrypted volume with the contents of the old one.
  • Improved handling of temporary errors that can occur when using the To Import folder with a library stored in NextCloud/OpenCloud.
  • It is now possible to override the source URL for a .eml file via AppleScript.
  • Updated the following sections of the manual:
  • Made various updates for Xcode 27 and macOS 27.
  • Fixed a bug due to a macOS change where changing a record’s label from the Info inspector didn’t work.
  • Fixed bug capturing emoji from Twitter.
  • Fixed a bug where temporary files were not deleted after capturing from Outlook.
  • Fixed a spurious error logged by the share extension.

If you have not installed a beta version of EagleFiler before, first click here to enter the beta key. Thereafter, you can just launch EagleFiler or choose Software Update from the EagleFiler menu to auto-install the beta. EagleFiler will also notify you about future betas automatically. You can click here to stop receiving in-app notifications of beta versions.

2

Maybe I’m being dense but I don’t see the link to download the beta? My eagle filer won’t launch after installing golden gate so I can’t update from in the app.

3

Which version of EagleFiler are you using? The 1.9.20 release version should work fine on Golden Gate, too, so if it’s not launching there may be something else going on. Please describe what’s happening when you try to open it. If the app launches but gets stuck opening a library, you can hold down the Shift key during launch to prevent EagleFiler from re-opening any libraries and then access the Software Update window to update EagleFiler.

4

1.9.19 – once I installed the above - it worked. (though it’s not taking my serial number/code)

5

Please make sure that you’ve entered both the Serial Name and the Serial Number as shown in your order confirmation e-mail. You can use Copy/Paste to make sure that they’re entered exactly or click the Serial Link to have EagleFiler enter them automatically.

6

Questions about latest beta upgrade:

  1. Worth doing beta upgrade from 1.9.20?
  2. Are there speed improvements to the current situation with Rosetta? I had trouble loading/launching in MacOS 26.5.2 (Previous post).
  3. Will opening time, errors passed to OS improve with EF Beta?
  4. Tested with MacOS 27.0?
EagleFiler future plans now that Rosetta will be phased out by MacOS28
7

There’s lots of good stuff in the 1.9.21 beta, but at this point you can skip the beta because it will be shipping soon.

The slowness in your previous post had nothing to do with Rosetta. It was because your library was offloaded from the Mac and had to be downloaded from cloud storage.

I’m not sure what the “to” is referring to—errors go the other direction from macOS to EagleFiler. But, yes, it does include improvements to the error handling.

Yes.