Xcode Canvas failed after updating to Big Sur and Latest Xcode.

Question

Created Nov ’20

Replies 10

Boosts 0

Views 3.4k

Participants 10

hi everyone
I have encountered a problem after updating to Big Sur this morning. my canvas preview won't work despite build succeed.
simulator is working.

the error code is Updating took more than 5 seconds
PreviewUpdateTimedOutError: Updating took more than 5 seconds

Updating a preview from ContentView_Previews in 2.RedMe.app (2495) took more than 5 seconds.
how can I fixed it?

system: Big Sur 11.0.1
Xcode: 12.2 version
many thanks

Boost

Answer 1

Developer Tools Engineer OP

Apple

Nov ’20

Sorry to hear you are having problems getting previews working. Probably best next step will be to file a feedback with diagnostics.
We will need the diagnostics Xcode Previews generates in order to make sure we understand the error the previews system is encountering.

When you get an error in Xcode Previews, an error banner appears in the canvas
Click the "Diagnostics" button in that banner
In the sheet that appears, click "Generate Report" in the bottom left of the sheet
Attach (or make from the folder) the resulting zip file to the bug (will be named something like previews-diagnostics-0123456789.zip)

Report back here with the feedback ID and I'll make sure it gets to the right team as soon as possible.

0

Answer 2

SkipHanson23 OP

Nov ’20

This happens on Catalina, xcode 12.2 as well. Even the most basic view (one Text()) object fails. Previews don't work at all.

This is causing a HUGE time suck with project development. A major feature set of xcode is useless at this point.

1

Answer 3

jammyman34 OP

Nov ’20

Exact same issue on a project I created (and worked many hours on) prior to updating to Big Sur.

I also created a brand new project as a test and it's giving me this error when I attempt to preview via canvas:

RemoteHumanReadableError: Failed to update preview.

Error encountered when sending 'previewInstances' message to agent.

==================================

| RemoteHumanReadableError: Unknown preview provider "ContentViewPreviews"
|
| TestAppName does not contain a preview provider named "ContentViewPreviews". Check your build settings to ensure the preview provider is compiled into your product.
|
| Mangled name: 0016TestAppName0021ContentViewPreviewsV

0

Answer 4

jammyman34 OP

Nov ’20

Per your request here is my feedback ID: FB8908497

0

Answer 5

KalyaniOSDeveloper OP

Dec ’20

Is there any resolution for the issue? Many developers I have known are also facing similar issue after updating to Big Sur. Apple team please resolve and let us know the fix ASAP.

1

Answer 6

mark-e-mark OP

Dec ’20

Did you get this working? Or figure out a work around?

Same issue after updating to 12.3 on Big Sur 11.1 (Mac Mini M1).

Update: it appears that the conversion to the latest settings for the project somehow changed the Signing Certificate from Development to Sign To Run Locally on my MacOS target. Once switched back, previews started working again.

May not be the issue others are having, but worth having a look as solved for me.

3

Answer 7

luantrindade OP

Dec ’20

Facing the exact same problem. I don't even know how to proceed in this case. Does anyone found any resolution? Cheers.

0

Answer 8

Starfia OP

Jan ’21

Whoa! The solution from mark-e-mark was the correct one in my case. Thank you so much – I would never have found that, and I don't think Xcode made any attempt to suggest it.

0

Answer 9

kevkevsmith OP

Jan ’21

previews-diagnostics-20210128-153427

that's the name of the folder that's created. when it happens to me. Not sure if this helps as mark-e-mark's solution didn't work for me

0

Answer 10

Morio64 OP

Nov ’21

Hi everyone,

a possible solution having worked out for me of this problem had already been posted over at stackoverflow by "sorceoror". Unfortunately I wasn't able to spot an answer going into this direction here on the official support page, so I decided on reposting his conclusion:

" I had the very same problem. Eventually, I figured out that this happens when the project name starts with a number character, e.g. "01-test". Creating a new project without the digit as a first character works just fine, e.g. "test". "

Hope I could help you ;-)

0