Xcode b4 Simulator "Posterboard has quit unexpectantly"

Has anyone had the issue where you load the simulator and it says "Posterboard has quit unexpectantly" and the background is all black and no the nice ios 16 default background. I submitted a feedback, and i have rebooted my pc etc to try the 'usuals'. Intel based mac here.

Curious if its just me. Simulator still works, but figured its not right.

Post not yet marked as solved Up vote post of lmDeveloper1 Down vote post of lmDeveloper1
4.7k views

Replies

I see this too. I'm using M1 pro. This is so annoying

Same here with Xcode B4 (M1 Pro). Had no issue on B3.

Also I've got 20% of constant CPU usage while running Xcode because of diagnosticd process, console shows a lot of errors from Posterboard. Reverting to B3.

Same problem, M1 Max, reverting to B3

I switched SDK to iOS 15.5 and all is good now, no crashes, no high CPU usage

Yeah, I'm seeing it too.

Still happening on beta 5. Submitted radar FB11180349

Here's a full stack trace:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: D4068785-7BC8-4156-9617-E3B34373F1CA
CrashReporter Key:   BB16E2CE-5877-09DE-B84C-67F22D8FB3DE
Hardware Model:      Mac14,2
Process:             PosterBoard [39705]
Path:                /Applications/Xcode-14.0-beta-5.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/Applications/PosterBoard.app/PosterBoard
Identifier:          com.apple.PosterBoard
Version:             1.0 (1)
Code Type:           ARM-64 (Native)
Role:                Non UI
Parent Process:      launchd_sim [39426]
Coalition:           com.apple.CoreSimulator.SimDevice.098D4305-4B5D-46A0-8C68-E47633230498 [9282]
Responsible Process: SimulatorTrampoline [37961]

Date/Time:           2022-08-09 19:27:41.7232 -0700
Launch Time:         2022-08-09 19:27:38.9224 -0700
OS Version:          macOS 12.5 (21G72)
Release Type:        User
Report Version:      104

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Triggered by Thread:  2

Last Exception Backtrace:
0   CoreFoundation                	       0x1032c02f0 __exceptionPreprocess + 160
1   libobjc.A.dylib               	       0x10197531c objc_exception_throw + 56
2   CoreFoundation                	       0x1032c000c -[NSException init] + 0
3   WallpaperKit                  	       0x1608220b0 -[WKWallpaperRepresentingCollectionsManager _loadSystemWallpaperCollections] + 1660
4   WallpaperKit                  	       0x16082135c -[WKWallpaperRepresentingCollectionsManager _loadCollections] + 260
5   WallpaperKit                  	       0x16082123c -[WKWallpaperRepresentingCollectionsManager initWithDownloadManager:loadLegacyContent:] + 156
6   WallpaperKit                  	       0x16081d5a0 __52+[WKDefaultWallpaperManager defaultWallpaperManager]_block_invoke + 72
7   libdispatch.dylib             	       0x107eb37c8 _dispatch_client_callout + 16
8   libdispatch.dylib             	       0x107eb4fbc _dispatch_once_callout + 28
9   WallpaperKit                  	       0x16081d554 +[WKDefaultWallpaperManager defaultWallpaperManager] + 60
10  PosterBoard                   	       0x100e23460 -[PBFWallpaperKitBridge defaultWallpaperIdentifier] + 36
11  PosterBoard                   	       0x100e234e0 -[PBFWallpaperKitBridge shouldInstallCollectionsPosterAsDefaultLockScreenWallpaper] + 20
12  PosterBoard                   	       0x100dd8380 -[PBFPosterExtensionDataStore _stateLock_setupSwitcherConfigurationForFirstTime] + 284
13  PosterBoard                   	       0x100dde520 -[PBFPosterExtensionDataStore _stateLock_updateExtensions:refreshDescriptors:powerLogReason:galleryUpdateOptions:queuedUpOperations:] + 5964
14  PosterBoard                   	       0x100de6084 -[PBFPosterExtensionDataStore posterExtensionProvider:foundExtensions:] + 116
15  PosterBoard                   	       0x100dfcde4 -[PBFPosterExtensionDefaultDataSource _queue_notifyDataStoreOfUpdatedExtensions:] + 552
16  PosterBoard                   	       0x100dfcac8 __44-[PBFPosterExtensionDefaultDataSource start]_block_invoke + 212
17  libdispatch.dylib             	       0x107eb37c8 _dispatch_client_callout + 16
18  libdispatch.dylib             	       0x107ec3f10 _dispatch_lane_barrier_sync_invoke_and_complete + 92
19  PosterBoard                   	       0x100dfc9e8 -[PBFPosterExtensionDefaultDataSource start] + 76
20  PosterBoard                   	       0x100dc8754 -[PBFPosterExtensionDataStore initWithURL:runtimeAssertionProvider:observer:wasMigrationJustPerformed:error:] + 884
21  PosterBoard                   	       0x100dc83b8 +[PBFPosterExtensionDataStore dataStoreAtURL:runtimeAssertionProvider:observer:wasMigrationJustPerformed:error:] + 96
22  PosterBoard                   	       0x100e33164 -[PBFPosterExtensionDataStoreXPCServiceGlue _dataStoreWithError:] + 492
23  PosterBoard                   	       0x100e3943c -[PBFPosterExtensionDataStoreXPCServiceGlue wallpaperPublisherDidReceiveObserverConnection] + 16
24  PosterBoardServices           	       0x10102caa8 -[PRSWallpaperPublisher listener:didReceiveConnection:withContext:] + 652
25  BoardServices                 	       0x103a2318c -[BSServiceConnectionListener didReceiveConnection:] + 228
26  BoardServices                 	       0x103a189c8 __42-[BSServiceDomain _initWithSpecification:]_block_invoke_3 + 356
27  BoardServices                 	       0x103a07adc __66-[BSXPCServiceConnectionEventHandler connection:handleConnection:]_block_invoke + 324
28  BoardServices                 	       0x103a2c188 BSXPCServiceConnectionExecuteCallOut + 232
29  BoardServices                 	       0x103a07844 -[BSXPCServiceConnectionEventHandler connection:handleConnection:] + 140
30  BoardServices                 	       0x103a2a114 __55-[BSXPCServiceConnection _lock_activateNowOrWhenReady:]_block_invoke_2 + 1512
31  libxpc.dylib                  	       0x1082e7404 _xpc_connection_call_event_handler + 68
32  libxpc.dylib                  	       0x1082e77c4 _xpc_connection_mach_event + 904
33  libdispatch.dylib             	       0x107eb387c _dispatch_client_callout4 + 16
34  libdispatch.dylib             	       0x107ed1f20 _dispatch_mach_msg_invoke + 624
35  libdispatch.dylib             	       0x107ebb6a8 _dispatch_lane_serial_drain + 348
36  libdispatch.dylib             	       0x107ed2fec _dispatch_mach_invoke + 468
37  libdispatch.dylib             	       0x107ebb6a8 _dispatch_lane_serial_drain + 348
38  libdispatch.dylib             	       0x107ebc4d4 _dispatch_lane_invoke + 448
39  libdispatch.dylib             	       0x107ec8624 _dispatch_workloop_worker_thread + 772
40  libsystem_pthread.dylib       	       0x10828fb40 _pthread_wqthread + 284
41  libsystem_pthread.dylib       	       0x10828e904 start_wqthread + 8

The same problem beta 4 Xcode 14 (PosterBoard)

The same happens in XCODE 14 Beta 5

For me, creating a new simulator from the Simulator organiser seemed to solve it, rather than using the pre-generated simulators. This was with Xcode 14b5.

Post not yet marked as solved Up vote reply of mnem Down vote reply of mnem

the same for me and the problem is that it closes actually only after 6 or 7 atempt to close it

Problem unresolved in XCode 14 beta 6. On M1 (non-pro/max models) CPU usage close to 100% at all heads, on MacBook Air cpu temperature constantly around 80—95º.

Same here, M1 Max machine and the issue still happens on Beta 6

Beta 6 has arrived, still the same issue. I have a suspicion, that it may be not Xcode per se, but some Ventura issue. It's strange that they ignoring the issue of an overheatng cpu.

EDIT: It solved problem in one place (with Picker), but not in other (with DatePicker).

  • I am using Monterrey and I am experiencing the same issue

Add a Comment

Just got the same problem (PosterBoard) with Xcode 14ß6, running on MacOS 12.5.1 when trying to run a WatchOS simulator.

Tested with Xcode 14ß5: unable to launch simulator.

Tested with Xcode 13.4.1: runs without problem.

I note that Xcode tries to use a Watch 6 simulator, where Xcode 13.4.1 proposes Watch 7:

On the left, with Xcode 14ß5, on the right with 13.4.1

I reinstalled Xcode 14ß6. And change for Series 7 simulator 45mm via iPhone 13 (vs Series 6 44mm via 13 Pro Max:

Looks like there is some mess with the simulators…

And that seems to work correctly, even though I finally got the Posterboard crash report….

Does anyone know what this PosterBoard is ? I read this on reddit:

I had a crash one time and the error reporting message said Posterboard crashed. I just assumed it was a new program used to run the lockscreen UI, similar to springboard.

So problem seems more related to iOS 16 simulator than watchOS…

  • Same Issue.

    iMac (Retina 5K, 27-inch, 2020) Monterey v12.5.1 Xcode 14.0 beta 6

    tried creating a new simulator. (Nope)Completely removed Xcode 13.4.1. AND 14.0 beta 6. Including: rm -rf /Developer & ~/DeveloperReinstalled 13.4.1 AND 14.0 beta 6 (Nope)
Add a Comment