I’m currently experiencing an issue where RapidWeaver Classic no longer opens on my machine. When I try to launch the application, I get an error message that says something along the lines of:
“Rapidweaver cannot be opened because of a problem – Please check with the developer to make sure Rapidweaver works with this version of macOS. You may need to reinstall the application. Be sure to install any available updates for the application and macOS.”
(Please note that I’m using a non-English macOS environment, so the exact wording may differ slightly on your system.)
My mac is running macOS 10.14.6 Mojave. After some checking, I realized that my installed version of RW had been updated to 9.5.0 — even though I don’t recall authorizing any update, and I thought I had auto-updates disabled.
As a fallback, I launched (the rock solid) version 9.3.4, which I had saved just in case of issues like this, and thankfully it runs without any problems.
So in summary, here’s what I’d like to report:
RapidWeaver 9.5.0 does not launch on macOS Mojave (10.14.6).
Somehow, the app seems to have updated itself to 9.5.0 without my explicit permission, despite auto-updates supposedly being disabled. Could you clarify how this might have happened?
RapidWeaver 9.5.0 does not launch on macOS Mojave (10.14.6).
Thanks for the heads-up, we’re looking into the issue and will ship an update shortly.
Somehow, the app seems to have updated itself to 9.5.0 without my explicit permission, despite auto-updates supposedly being disabled. Could you clarify how this might have happened?
RapidWeaver never has and never will auto-update in the background; it ALWAYS prompts you to download and install the update.
If anyone else on Mojave is reading this and has run into the issue, you can download 9.4.3 from here.
Thank you so much! The new build opened without any issues on macOS Mojave — much appreciated.
That said, I still can’t shake off some doubts regarding the version update that seems to have happened automatically. I had a similar experience before, when the version jumped from 9.3.x to 9.4.x. Even though I hadn’t explicitly triggered an upgrade, the app somehow updated itself, which then caused stability issues — that’s actually why I always keep a copy of 9.3.4 safely stored, just in case.
Of course, I don’t have concrete evidence of exactly how or under what conditions this happened. But if there’s any chance that this kind of automatic update could occur, it might be worth looking into, just to be sure.
Glad to hear you’re back up and running. I can also assure you an update will never be installed without your consent (it’s impossible for the app to do that with the code we’ve written). You’ll ALWAYS need to click the update button to make it happen.
