Unhooked addons folder?

Posting this here, instead of general bug report to RMS just in case other folks are tackling similarly intractable support problems like these.

I have 3 open support tickets right now all with suspiciously similar symptoms:

  • Crazy crashing
  • Plugins/Stacks not loading/installing
  • Reinstallation doesn’t help – sometimes make it worse

I managed to solve one of these and the end solution is kind of crazy. Basically their custom addons location had somehow become really really confused.

Inside RapidWeaver their custom location looked OK. And if they clicked the Reveal in Finder it would pop up the custom folder.


RapidWeaver was clearly not using that folder. It was somehow defaulting back to the standard App Support folder. The user had an old copy of Stacks and other stuff in there. That is the Stacks that was running – and the stacks in that folder were the ones that showed up inside Stacks.

The way we fixed it was to manually disable the custom location. Then restart RW. Then re-add the custom location. The restart RW. That seemed to get things back to normal.

I don’t know how this happened – the user said it was “during a recent Stacks update”. That seems a bit dubious to me. He also had High Sierra and had done the most recent RW update too – so perhaps the update or APFS unhooked something?

@dan @simon : two questions:

  1. could the bookmark-object that RW uses to store the custom location of the addons folder get mangled by the High Sierra update? or something else?

  2. if RW does, for whatever reason, get a bad fileURL to the custom location… what’s the expected error behavior there? it seems like silently falling back to the old folder might be it – which seems like it’s generally going to cause pretty serious problems.

@simon: suggestion: if the addons folder can’t be found: start up in “safe” (no addons) mode. and throw up an alert that lets the user reset the location.

why: starting up with ancient addons has the potential for losing data or damaging their file. “safe” mode, while useless, helps the user solve the problem immediately. sort of NSParamameterAssert – but for addons. :stuck_out_tongue_closed_eyes:

Hey @isaiah,

Thanks for reporting this. Your second point about RapidWeaver silently falling back to the old folder is correct - well spotted!

This could be for a whole load of reasons - any reason that would cause a security scoped bookmark to stop resolving. I’m unsure if upgrading to High Sierra would cause that - I’d hope not, but it honestly wouldn’t surprise me.

I’ve just uploaded a beta build that will potentially “fix” this issue - if this situation happens again, the user will be prompted to select their addon location again (and relaunch RapidWeaver). I don’t think there’s any real way for us to predict when it’ll happen and work around the issue before it does - for whatever reason, macOS just decides to stop resolving the bookmark.

You can download the latest 7.5.2 beta here:

Let me know how it works out for you.



Very nice. Thanks for the quick action on this. I think it’ll definitely help – even if it is a (I hope) rare occurrence.


1 Like