SwiftUI / Xcode Error - Updating took more than 5 seconds

Question

When I try to preview one of my views in the canvas I keep getting the following error:

PreviewUpdateTimedOutError: Updating took more than 5 seconds

All my other views load perfectly fine.

Why is this happening and how do I resolve?

I am using SwiftUI in Xcode 11.4 (public release)

Make build entire project before; brake your view on to smaller parts. — Asperi, Apr 02 '20 at 09:20
I have it all the time with the new Xcode 11.4 It was all good before. Actually this version have introduced tons of issues in a SwiftUI project I'm working on. — zh., Apr 13 '20 at 17:15
As @Asperi have mentioned, try to have less previews at the same time, brake your code into smaller pieces. But it is still unpredictable – same code might render well now and start to have this "5 seconds" issue a minute after. Actually I've found this question looking for a solution to fix it. To continue execution and rendering longer than 5 seconds. No luck though. — zh., Apr 13 '20 at 17:20
I also forgot to put a dot before one of the subViews attributes. — Vera Chen, Dec 23 '20 at 08:40
I just have a separate project for previews that only contains UI, nothing else. Make it as easy as possible for the compiler. — aheze, Apr 29 '21 at 15:37

score 34 · Answer 1 · answered Apr 26 '21 at 05:29

34

I stopped using the simulator and chose "Any iOS Device" and that solved the problem.

answered Apr 26 '21 at 05:29

tichise

489
4
3

1

This solution helps a lot. As far as I can tell though, there is no fool-proof way to get around this. – Christopher Shireman May 25 '21 at 17:59
This only solution worked for me ! even contacted Apple did not solve the issue . but chose Any iOS Device is solved the issue . – Hussain1982 Mar 17 '22 at 18:24
This solution works immediately, thanks! (Xcode 13.2.1) – Michael Pohl Apr 07 '22 at 17:42
Also, any other device other than the one the simulator is using works too. – Brainware May 08 '22 at 22:58
But, my apologies, who could tell me why this happened? – Neal.Marlin Jul 05 '22 at 11:21

score 16 · Answer 2 · answered Dec 17 '20 at 14:51

16

In my case the issue was this line in Build settings:

Something I did accidentally changed signing settings in my project. Specifically, "signing identity" was set to "Sign to Run Locally.". For some reasons, SwiftUI Previews don't work then.

Simply deleting this line from build settings (aka setting default value) solved the problem.

answered Dec 17 '20 at 14:51

msmialko

1,439
2
20
35

Xcode 12.4 (macOS 10.15.7) This fixed it. – soundflix Nov 15 '22 at 12:08

score 10 · Answer 3 · answered Jan 18 '21 at 21:23

10

Some time, the error displaying is not the real error.

For me it was because i missing : .environmentObject(...)

answered Jan 18 '21 at 21:23

YanSte

10,661
3
57
53

score 10 · Answer 4 · edited Jan 17 '22 at 04:56

As of Xcode 12.5.1, the message PreviewUpdateTimedOutError: Updating took more than 5 seconds most likely means that your app crashed and thus updating the preview failed. The real reason for the crash is unfortunately obscured by this useless message (why Apple would do that is beyond me). To get at the real reason, you'll need to:

click Diagnostics at the top of the preview next to the useless error message
in the next dialog, click Generate Report > Reveal in Finder

This will take a bit. Then Finder will open with a folder highlighted. Open that folder. Inside you'll see a lot of log files and folders.

If your app indeed crashed, you'll see a folder called CrashLogs which contains crash logs for your app, including the error message and stack trace. This should help you resolve the actual error causing the preview to break.

Note that for me, sometimes the CrashLogs were not included in the report even though my app really did crash. Retrying the preview and generating another report fixed this for me. The whole error reporting process seems to be rather unstable for the previews, unfortunately.

score 8 · Answer 5 · answered Aug 15 '20 at 09:10

8

Try Clean (Shift + ⌘ + K) and Build (⌘ + B) to build again the SwiftUI project, it works in Xcode 11.6. Try building a basic hello world app.

answered Aug 15 '20 at 09:10

Mohit

891
10
25

score 5 · Answer 6 · answered Dec 27 '20 at 14:55

In my case the issue was that the PreviewProvider was marked private. Simply make it internal or remove the private access modifier.

private /* <- remove */ struct YourView_Previews: PreviewProvider {
    static var previews: some View {
        // Your previews
    }
}

Noor Hossain · Answer 7 · 2022-04-13T22:31:44.140

5

I am using Version 13.2.1 (13C100). I have Clean (Shift + ⌘ + K) and Build (⌘ + B) the project. But, the problem remains.

Then, just restarted Xcode. And the problem gone.

edited Apr 13 '22 at 22:31

answered Mar 04 '22 at 18:09

Noor Hossain

1,620
1
18
25

1

I had the exact same experience on the same version of Xcode. It was working just fine and started happening out of nowhere. A simple restart of Xcode fixed it. – Ruiz Apr 13 '22 at 15:17

score 2 · Answer 8 · answered Jul 13 '20 at 07:43

In my case viewModel required to display SwiftUI_preview was doing a call to a CoreData (fast call) in the init of the viewModel.

Moved actual call of that "reload() method" so it's not called on preview, fixed.

(I believe the correct way is to use mocked protocol instead of instance of the viewModel)

score 2 · Answer 9 · answered Nov 16 '20 at 18:49

2

If you have an .onAppear clause, try commenting that out for preview.

answered Nov 16 '20 at 18:49

Dan Selig

234
2
11

So I'm having this same issue every since I updated to Big Sur. I'm using Xcode v12.2. I commented out the .onAppear clause and then xcode game me this error instead of the 5 sec timout "Check your build settings to ensure the preview provider is compiled into your product." What the heck does that mean? – jammyman34 Nov 18 '20 at 20:54

score 2 · Answer 10 · answered Dec 06 '20 at 17:25

None of these suggestions helped me but I did discover that you can't rely entirely on a successful build to pick up all issues. In my case I had '.modifier(modifier:)' entered incorrectly as 'modifier(modifier:)'. My code built successfully but my preview did not work until I added the period before modifier.

score 2 · Answer 11 · answered Jan 29 '21 at 09:17

2

For me the issue was related to a force unwrapping of an element not being found at preview time.

Note: Always check the diagnostics report. The issue will be at the top section after termination reason.

answered Jan 29 '21 at 09:17

user7684436

697
14
39

score 1 · Answer 12 · answered Jul 28 '20 at 15:04

1

In my case the canvas/screen size was smaller than the content, so simply wrapping my content in the scrollView do remove the error and displaying the content in the canvas.

answered Jul 28 '20 at 15:04

Peter Andrew

11
1

score 1 · Answer 13 · edited Jan 17 '22 at 04:58

1

I had this issue as well, and nothing fixed the problem. I am now on 11.6 and after updating the issue went away. I think it might be a problem with Xcode 11.4.

I'd suggest updating Xcode if possible.

edited Jan 17 '22 at 04:58

shim

9,289
12
69
108

answered Aug 20 '20 at 17:27

Matthew S.

239
2
7

score 1 · Answer 14 · answered Feb 19 '21 at 21:46

I had a fatalError("...") in my code, which I only figured out after reading the diagnostic logs. Would be nice if SwiftUI actually hinted this!

You can get the diagnostics by clicking "Diagnostics" next to "Try Again" at the top of the preview window.

To summarise lots of answers here, it seems that the preview taking a while to update is the equivalent of a crash, when running on a real device or on the simulator.

score 1 · Answer 15 · answered Apr 29 '21 at 15:27

1

First comment out all the environment Objects are used for the particular View. Once you get preview then uncomment it to run the build. This trick works for me

//@EnvironmentObject var observerObj:PropertyObserver

answered Apr 29 '21 at 15:27

RakeshDipuna

1,570
13
19

score 0 · Answer 16 · answered Apr 23 '20 at 08:41

0

In SwiftUI, you couldn't add more than 10 subviews into your contentview, otherwise it couldn't compile.

answered Apr 23 '20 at 08:41

滕诗雨

19

score 0 · Answer 17 · answered Nov 11 '20 at 12:18

I had the same problem, then I started to comment out the subViews inside my main view, one by one & try to preview again then I found out the problem was caused because I forgot to put a dot before one of the subViews attributes.

So that's how I fixed it.

score 0 · Answer 18 · answered Jan 14 '21 at 16:27

The reason is because its unable to find the landmarkData.json file. To resolve this,

select landmark.json file in Resources.
Show Inspectors ( top right icon )
Select show file inspector
Under Target membership, select / check Landmarks

This should resolve the preview issue.

score 0 · Answer 19 · answered Feb 12 '21 at 09:20

0

For some reason, in SwiftUI, when I embeded Text in Scroll View and VStack, this error occurred. After few unsuccessful attempts to fix this by clearing and building project, I deleted code and wrote it down again, same as it was. Now it is working.

answered Feb 12 '21 at 09:20

Vladimir Sukanica

475
4
11

score 0 · Answer 20 · answered Feb 27 '21 at 16:41

0

I had my run device set to a real device I use for testing. When I changed that to one in the simulator it started working again.

answered Feb 27 '21 at 16:41

Jevon Charles

644
1
7
12

Dilts · Answer 21 · 2021-04-09T23:51:15.573

Similar to @YannSteph, this happened to me because I put the .environmentObject() at the app entry point where it creates the first view:

@main
struct RecipeApp: App {
    var body: some Scene {
        WindowGroup {
            RecipeTabView()
                .environmentObject(RecipeModel())
        }
    }
}

But this prevented the preview from working. I thought I was being smart putting it there, so all the views could have access to it, but it just crashed the preview.

Moving it back into the main View.Swift file that is my app's starting view fixed the preview issue.

^^^ EDIT: Ran into this again when I didn't put the .environmentObject() in the struct for the preview. Probably a rookie mistake but there appears to be many ways to trigger this error.

score 0 · Answer 22 · answered May 22 '21 at 14:36

I had the same issue after creating a brand new Multiplatform App project using Xcode 12.5. Based on the solutions above I followed a hunch and now believe that the issue is due to invalid path parameters.

After renaming the Schemes and Targets from (iOS) to .iOS (and the same for macOS), to remove spaces and brackets, it is now working.

score 0 · Answer 23 · answered Aug 31 '21 at 09:11

I had this issue after changing bundle id and signing from personal to team.

After changing device to Any device as advised here, I received another error description, saying

Could not install the preview host "AppName.app" on iPhone 12 Pro Max

agentBundle = com.bundle.Its.AppName { url: file:///Users/macbookair/Library/Developer/Xcode/DerivedData/AppName-> desupjbpqvjlegfbskxydixpouvc/Build/Intermediates.noindex/Previews/AppName/Prod> ucts/Debug-iphonesimulator/AppName.app > version: 49557 signingInformation: Code Signing { identifier: com.bundle.AppName hasGetTaskAllow: false isSandboxed: false } }

Clean build, deleting Derived, Deleting all apps installed on simulators, cleaning Xcode Cache, restarting Xcode and Mac didn't help.

What had helped was creating new project with initially correct bundle id and copying all my files there.

score 0 · Answer 24 · answered Oct 04 '21 at 07:47

0

I have got into the same issue on Xcode 12.4, but the code works fine on Xcode 13.0.

answered Oct 04 '21 at 07:47

Paramasivan Samuttiram

3,728
1
24
28

score 0 · Answer 25 · answered Jan 04 '22 at 20:18

I was following the IOS App Dev Tutorial, where one creates an app named ScrumDinger. I ran into this issue at Displaying Data in List

In my case the problem was that I wrote in CardView.swift

HStack {
     Label("\(scrum.attendees.count)", systemImage: "person.3")
     accessibilityLabel("\(scrum.attendees.count) attendees")

instead of

  HStack {
      Label("\(scrum.attendees.count)", systemImage: "person.3")
      .accessibilityLabel("\(scrum.attendees.count) attendees")

The missing dot before accessibilityLabel was the problem.

Tutorial: https://developer.apple.com/tutorials/app-dev-training/displaying-data-in-a-list

score 0 · Answer 26 · answered Mar 10 '22 at 11:09

0

In my case the issue was that I was trying to preview a view with a fixed width (.previewLayout(.fixed(width: 344, height: 220))) wider than the selected simulator (iPhone SE 1st generation)

answered Mar 10 '22 at 11:09

Carlos

1,121
12
26

score 0 · Answer 27 · answered May 03 '22 at 19:52

0

I get this error often. My last time of occurrence, I had "gesture" instead of ".gesture". Usually its best to just need to find the error in your code yourself because Xcode does not point out the issue directly.

answered May 03 '22 at 19:52

Americana American

59
1
3

score 0 · Answer 28 · answered Jul 18 '22 at 00:07

I only had Xcode 14 Beta installed on my machine and the previews did not work. All of the other answers did not work for me.

Installing Xcode 13.4.1 and running the preview with it did solve my problems and now I can also see the preview in Xcode 14 Beta as well.

score 0 · Answer 29 · answered Dec 12 '22 at 23:57

0

In my case, I disabled automatic canvas refresh by going to Editor -> Canvas -> Automatically Refresh Canvas and making sure it.

Then I use ⌥⌘P (Command-Option-P) to refresh the canvas preview.

answered Dec 12 '22 at 23:57

Taylor M

1,855
1
14
20

SwiftUI / Xcode Error - Updating took more than 5 seconds

29 Answers29