RapidWeaver 8.4 Beta 1

Hello Weavers,

RapidWeaver 8.4 adds compatible for macOS Catalina, version 10.15 and is of course the best version of RapidWeaver yet.

What’s New in 8.4?

  • Fixed a crash when right clicking a link in Styled Text (Catalina)
  • Fixed some thread issues in (Catalina)
  • HTML page no longer looses “show in navigation” setting when migrating from RW7 to RW8
  • Fixed an issue with AmazonS3 showing access denied on some files
  • Various other fixes and improvements to keep RapidWeaver running smoothly

Please remember that this is a beta and may contain bugs, please backup your projects before using this version.

Download RapidWeaver 8.4 (20812b) Beta 1

Happy Weaving!

Team Realmac


Is this a bug?

I am now using Tags with the Rapidweaver Built In Blog. For some reason the sort order for a tag “page” isn’t based on the date of the blog entry. It may be based on when I actually created the blog entry. This is different than a category page which seems to respect the blog entry date.

As an example … here’s my tag page for a Venue called “The Rust Belt”.

For some reason the entry for Arkansauce (8 Aug 2019) is completely out of order.

If you look at my Category page for “Concerts”, that entry is in the correct order.

Thanks for your help.


BTW - It would be really cool to also see a column for Tags in the Rapidweaver Blog Edit Window. Today I have columns for Title, Categories, and Date Created. I don’t see how to display a column for “Tags”.

No previews at all for my 2 sites:

Anyone else seeing the above export issue?

@bwil Also, have you tried to re-specify the Export folder again? Perhaps it’s been moved…

I set the export location and there was no change in the error message. A new project was fine. Then I gave Rapidweaver full hard disk access, restarted Rapidweaver and now I can get a preview. I don’t understand why there is a difference between an old and a new project. And Catalina should have asked for folder access.

Got a nil object exception just now when trying to preview:

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [23831]

Application Specific Information:
Crashing on exception: *** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[4]

Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff3a2026f3 __exceptionPreprocess + 250
1 libobjc.A.dylib 0x00007fff6fcd7bd4 objc_exception_throw + 48
2 CoreFoundation 0x00007fff3a2c509a _CFThrowFormattedException + 202
3 CoreFoundation 0x00007fff3a2cfaab -[__NSPlaceholderDictionary initWithObjects:forKeys:count:].cold.5 + 0
4 CoreFoundation 0x00007fff3a11f2ad -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 235
5 CoreFoundation 0x00007fff3a15b3a6 +[NSDictionary dictionaryWithObjects:forKeys:count:] + 59
6 Stacks 0x000000010918f84a -[YHCompiledTemplate renderForNode:slice:] + 1034
7 Stacks 0x0000000109138610 -[YHNode newInnerPreviewWithCompiled:] + 784
8 Stacks 0x00000001091382d9 -[YHNode newInnerPreview] + 57
9 Stacks 0x0000000109137937 -[YHNode innerPreview] + 87
10 Stacks 0x000000010913d238 -[YHNode editModeHTML] + 1080
11 Stacks 0x0000000109129c94 __25-[YHNode refreshWithUid:]_block_invoke + 68
12 libdispatch.dylib 0x00007fff70fe3553 _dispatch_call_block_and_release + 12
13 libdispatch.dylib 0x00007fff70fe44de _dispatch_client_callout + 8
14 libdispatch.dylib 0x00007fff70fefbd3 _dispatch_main_queue_callback_4CF + 1105
15 CoreFoundation 0x00007fff3a151d00 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 9
16 CoreFoundation 0x00007fff3a15144a __CFRunLoopRun + 2370
17 CoreFoundation 0x00007fff3a150883 CFRunLoopRunSpecific + 499
18 HIToolbox 0x00007fff38ce5f1d RunCurrentEventLoopInMode + 292
19 HIToolbox 0x00007fff38ce5c5d ReceiveNextEventCommon + 600
20 HIToolbox 0x00007fff38ce59e7 _BlockUntilNextEventMatchingListInModeWithFilter + 64
21 AppKit 0x00007fff37393f5c _DPSNextEvent + 990
22 AppKit 0x00007fff37392ccc -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
23 AppKit 0x00007fff3738d466 -[NSApplication run] + 658
24 AppKit 0x00007fff3737f332 NSApplicationMain + 777
25 libdyld.dylib 0x00007fff710342a5 start + 1

@bwil can you let us know what version of Catalina you are using?

Many Thanks

Beta 7, not using the public beta. I need to update to beta 8 in the next days.

@bwil Please update to beta 8, I hit a number of significant sandbox related problems in beta 7 and pretty sure I saw preview issues too.

The nil object exception looks to originate from Stacks so @isaiah may need to look at that one.

Catalina beta 7 has the potential to corrupt documents so please update as soon as you can.

Updated to latest beta.

I removed the full disk access and used the original file from my main dev machine. The error shows up again. After setting the export folder the error remains.29

Forgot to add: the error remains even after restarting Rapidweaver.

I’m guessing this is caused by you removing full disk access… If you grant RapidWeaver access to the full disk do you still see the error?

Yes, if I grant Rapidweaver full disk access then the error is gone. However, the error message should say something sensible. And if Rapidweaver wants access to a folder I should get one of those wonderful wonderful dialogs requesting access to the folder.

Click undo a couple of times:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [3332]

Application Specific Information:
Crashing on exception: undoNestedGroup: NSUndoManager 0x600003f86b20 is in invalid state, call endUndoGrouping before calling this method


Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff310b6033 __exceptionPreprocess + 250
1 libobjc.A.dylib 0x00007fff670c4bd4 objc_exception_throw + 48
2 Foundation 0x00007fff33833375 -[_NSUndoStack setDiscardable:] + 0
3 AppKit 0x00007fff2e4f0434 -[NSApplication(NSResponder) sendAction:to:from:] + 299
4 AppKit 0x00007fff2e545552 -[NSMenuItem _corePerformAction] + 312
5 AppKit 0x00007fff2e5452ce -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 106
6 AppKit 0x00007fff2e54410e -[NSMenu performKeyEquivalent:] + 348
7 AppKit 0x00007fff2e9b302f routeKeyEquivalent + 521
8 AppKit 0x00007fff2e245e34 -[NSApplication(NSEvent) sendEvent:] + 1072
9 AppKit 0x00007fff2e2353c6 -[NSApplication run] + 707
10 AppKit 0x00007fff2e2271c6 NSApplicationMain + 777
11 libdyld.dylib 0x00007fff684232a5 start + 1
12 ??? 0x0000000000000001 0x0 + 1

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.AppKit 0x00007fff2e5ea89b -[NSApplication _crashOnException:] + 106
1 com.apple.AppKit 0x00007fff2e5ea775 -[NSApplication reportException:] + 908
2 com.realmacsoftware.rapidweaver8 0x0000000102824820 CLSNSApplicationReportException(objc_object*, objc_selector*, NSException*) + 69
3 com.apple.AppKit 0x00007fff2e235447 -[NSApplication run] + 836
4 com.apple.AppKit 0x00007fff2e2271c6 NSApplicationMain + 777
5 libdyld.dylib 0x00007fff684232a5 start + 1

RW got stuck the second time loading the stack list:

If anyone has any more info about this, please send my way. I can guard against that nil, of course, but it’s a strange place to see it. It’s likely that it has something to do with the particular stack that the template compiler is working on.

I’m getting that too but using RW 8.3 and Stacks 4. Don’t know if it works for you but clicking on a page in your project seems to clear it.

Yep. Seems to be a Stack4 problem.

if anyone can describe how to reproduce the problem I can probably easily make it go away. probably in just a day or two.

but right now i’m afraid I don’t have enough info to see the problem.

just telling me what you’re doing when the problem occurs is probably enough. a file that helps make the problem happen is even better.

you will help yourself and your fellow weaver’s if you just take a minute and type a sentence or two about the issue.


Hi @isaiah
I sent in a ticket about it and what seemed to trigger it, I can send in project files too if you can let me know where to send them too