People have had the issue since Xcode 12 beta 4, the issue is not resolved in beta 5 either.
Does anyone at Apple actually builds for watchOS 7 or deploys apps for testing?
Incident Identifier: AA267F2C-127A-4961-89D1-ED2EEA7A82ED
Hardware Model:			Watch4,1
Process:						 AppName WatchKit Extension [276]
Path:								/private/var/containers/Bundle/Application/837F23DD-16E4-4626-A184-F19464DBDC0E/AppName WatchKit App.app/PlugIns/AppName WatchKit Extension.appex/AppName WatchKit Extension
Identifier:					com.appersian.AppName.watchkitapp.watchkitextension
Version:						 7 (1.0)
AppVariant:					1:Watch4,1:7
Beta:								YES
Code Type:					 ARM (Native)
Role:								Non UI
Parent Process:			launchd [1]
Coalition:					 com.appersian.AppName.watchkitapp [336]
Date/Time:					 2020-08-18 21:20:46.3291 +0430
Launch Time:				 2020-08-18 21:20:46.0000 +0430
OS Version:					Watch OS 7.0 (18R5350e)
Release Type:				User
Baseband Version:		n/a
Report Version:			104
Exception Type:	EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:	EXC_CORPSE_NOTIFY
Termination Reason: Namespace WATCHKIT, Code 0x1
Triggered by Thread:	0
Thread 0 name:
Thread 0 Crashed:
0	 libsystem_kernel.dylib				 0x20b31060 __abort_with_payload + 8
1	 libsystem_kernel.dylib				 0x20b3597c abort_with_payload_wrapper_internal + 100 (terminate_with_reason.c:102)
2	 libsystem_kernel.dylib				 0x20b35918 abort_with_reason + 28 (terminate_with_reason.c:116)
3	 WatchKit											 0x36bb2510 __abort_with_reason + 128 (SPUtils.h:15)
4	 WatchKit											 0x36bb3654 __68-[SPApplicationDelegate application:_didFinishLaunchingWithOptions:]_block_invoke + 2880 (SPApplicationDelegate.m:0)
5	 libdispatch.dylib						 0x2095b244 _dispatch_client_callout + 16 (object.m:559)
6	 libdispatch.dylib						 0x2095c8a8 _dispatch_once_callout + 28 (once.c:52)
7	 WatchKit											 0x36b0f978 -[SPApplicationDelegate application:_didFinishLaunchingWithOptions:] + 584 (once.h:84)
8	 WatchKit											 0x36b0f70c -[SPApplicationDelegate application:didFinishLaunchingSuspendedWithOptions:] + 196 (SPApplicationDelegate.m:726)
9	 UIKitCore										 0x421fe324 -[UIApplication _callInitializationDelegatesWithActions:forCanvas:payload:fromOriginatingProcess:] + 3832 (UIApplication.m:2634)
10	UIKitCore										 0x422040ec -[UIApplication _runWithMainScene:transitionContext:completion:] + 1148 (UIApplication.m:4236)
11	UIKitCore										 0x41a049c4 -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 216 (_UISceneLifecycleMultiplexer.m:427)
12	UIKitCore										 0x421ffe0c -[UIApplication _compellApplicationLaunchToCompleteUnconditionally] + 64 (UIApplication.m:3231)
13	UIKitCore										 0x42200248 -[UIApplication _run] + 1068 (UIApplication.m:0)
14	UIKitCore										 0x42205908 UIApplicationMain + 140 (UIApplication.m:4787)
15	WatchKit											 0x36b0ee80 WKExtensionMain + 300 (main.m:34)
16	libdyld.dylib								 0x2099c974 start + 4
Thread 1:
0	 libsystem_pthread.dylib			 0x20bb65b4 start_wqthread + 0
Thread 2:
0	 libsystem_pthread.dylib			 0x20bb65b4 start_wqthread + 0
Thread 3:
0	 libsystem_pthread.dylib			 0x20bb65b4 start_wqthread + 0
Thread 4:
0	 libsystem_pthread.dylib			 0x20bb65b4 start_wqthread + 0
Thread 5 name:
Thread 5:
0	 libsystem_kernel.dylib				 0x20b0e8a4 mach_msg_trap + 8
1	 libsystem_kernel.dylib				 0x20b0dd00 mach_msg + 72 (mach_msg.c:103)
2	 CoreFoundation								 0x20f28bcc __CFRunLoopServiceMachPort + 376 (CFRunLoop.c:2641)
3	 CoreFoundation								 0x20f23100 __CFRunLoopRun + 1184 (CFRunLoop.c:2974)
4	 CoreFoundation								 0x20f22740 CFRunLoopRunSpecific + 572 (CFRunLoop.c:3242)
5	 Foundation										 0x21a77520 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 228 (NSRunLoop.m:374)
6	 Foundation										 0x21a77400 -[NSRunLoop(NSRunLoop) runUntilDate:] + 88 (NSRunLoop.m:421)
7	 UIKitCore										 0x42299f60 -[UIEventFetcher threadMain] + 152 (UIEventFetcher.m:761)
8	 Foundation										 0x21bd6ccc NSThreadstart__ + 844 (NSThread.m:724)
9	 libsystem_pthread.dylib			 0x20badf04 _pthread_start + 288 (pthread.c:880)
10	libsystem_pthread.dylib			 0x20bb65c8 thread_start + 8
Thread 0 crashed with ARM Thread State (64-bit):
		x0: 0x0000000000000016	 x1: 0x0000000000000001	 x2: 0x0000000000000000	 x3: 0x0000000000000000
		x4: 0x0000000013773df9	 x5: 0x0000000000000002	 x6: 0x0000000000000000	 x7: 0x0000000000000000
		x8: 0x0000000000000020	 x9: 0x00000000da2c00fa	x10: 0x000000004e4f7c00	x11: 0x0000000000000000
	 x12: 0x0000000000ff0007	x13: 0x000000001a324000	x14: 0x0000000000033fe8	x15: 0x0000000000000000
	 x16: 0x0000000000000209	x17: 0x0000000000000001	x18: 0x0000000000000000	x19: 0x0000000000000002
	 x20: 0x0000000013773df9	x21: 0x0000000000000000	x22: 0x0000000000000000	x23: 0x0000000000000001
	 x24: 0x0000000000000016	x25: 0x000000004f908478	x26: 0x0000000013660460	x27: 0x000000000000000c
	 x28: 0x00000000515d0000	 fp: 0x0000000002cb7350	 lr: 0x0000000020b3597c
		sp: 0x0000000002cb7310	 pc: 0x0000000020b31060 cpsr: 0x40000000
	 esr: 0x56000080	Address size fault
Post
Replies
Boosts
Views
Activity
I have noticed that emoji characters in watchOS are rendered in lower quality than iOS or macOS (i.e. size 80), I fail to understand whether this is an expected behavior due to limited Watch storage or I'm missing something?
P.S. I can't attach screenshots here?!