Has Summer 18 broken Skuid pages in a Community templates?

I have a project in a scratch org that’s built on the Partner Central community template, and embeds Skuid pages.

Over the weekend, my scratch org was upgraded to Summer 18, and it appears that something has changed that breaks Skuid pages. In the console, I get an error “Invalid XML” and then a dump of the page XML, with the following beneath it:

&nbsp; &nbsp; at Function.error (skuid__JQueryJS:1)<br>&nbsp; &nbsp; at Function.na.parseXML (skuid__JQueryJS:3)<br>&nbsp; &nbsp; at Object.vb [as makeXMLDoc] (skuid__SkuidJS:6)<br>&nbsp; &nbsp; at eval (skuid__SkuidJS:24)<br>&nbsp; &nbsp; at l (skuid__JQueryJS:2)<br>&nbsp; &nbsp; at Object.m (skuid__JQueryJS:2)

The page still works with an internal user. I also updated the community to point to a much simpler Skuid page (basically “Hello World”), and the same error occurs.

My guess is that the way the page XML is being returned from Apex has changed in some way for Community users, that’s breaking whatever is used to parse the page XML.

Seems so. Summer 18 wrecked all of our pages in Lightning. 

Hi Gary and Josef~

Please see this community announcement. All updates will be made there.

Thanks!
Karen