Question

我们最近提交了两个应用程序（一个新的应用程序，其中一个是已发布的应用程序的更新），并且由于以下原因让iOS应用程序审核小组拒绝了这两个应用程序：

准则2.1 - 表现在我们审核期间，您的应用在连接到IPv6网络的运行iOS 11.2.5的iPad或iPhone上崩溃了。

在提交应用程序之前，我们在4个不同的设备和iOS版本上使用testflight进行了广泛的测试，并且没有遇到任何崩溃。我们无法重现ios应用审核小组体验的崩溃

我们的开发环境对于两个应用程序是相同的，可能这是导致崩溃的原因： Unity 2017.2.1f1与Vuforia（这是一个增强的现实应用程序），Xcode 9.2（最新版本）

Herafter你会发现新应用程序的崩溃日志，（更新的应用程序有一个相同的崩溃日志......），它们非常相似：

The two crashlogs are very similar : 

{"app_name":"ournewappname","timestamp":"2018-03-01 17:04:56.02 -0800","app_version":"1.0.1","slice_uuid":"af7e5c57-c2bc-3c91-8e1e-559acfccdb7f","adam_id":0,"build_version":"1","bundleID":"fr.ourcompany.ournewappname","share_with_app_devs":false,"is_first_party":false,"bug_type":"109","os_version":"iPhone OS 11.2.5 (15D60)","incident_id":"002164F5-FD42-4A49-BF58-E8C1CB773010","name":"ournewappname"}

Incident Identifier: 002164F5-FD42-4A49-BF58-E8C1CB773010
CrashReporter Key:   6fa54cb83ccb006df1d056599e75f6797f1ac664
Hardware Model:      iPad5,1
Device Model:        J96AP
Process:             ournewappname [4216]
Path:                /private/var/containers/Bundle/Application/752BA8CA-A7AE-4823-976E-1D5DEBD34B2E/ournewappname.app/ournewappname
Identifier:          fr.ourcompany.ournewappname
Version:             1 (1.0.1)
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd.development [1]
Coalition:           fr.ourcompany.ournewappname [1066]


Date/Time:           2018-03-01 17:04:55.8059 -0800
Launch Time:         2018-03-01 17:04:54.7575 -0800
OS Version:          iPhone OS 11.2.5 (15D60)
Baseband Version:    n/a
UDID:                a728c3d680bc84aaaddc473d254d3c02a764955f
Report Version:      104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000088
VM Region Info: 0x88 is not in any region.  Bytes before following region: 4301520760
      REGION TYPE                      START - END             [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                 0000000100640000-0000000100644000 [   16K] r-x/r-x SM=COW  ...ealtwrarcard]

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
Triggered by Thread:  0

Filtered syslog:
Timestamp               Thread     Type        Activity             PID
2018-03-01 17:04:54.8314 -0800  0xfd29 1024 0x0 4216 AssertionServices: BKSWorkspace created.
2018-03-01 17:04:54.9677 -0800  0xfd29 1024 0x0 4216 AccessibilitySettingsLoader: Loading settings loader: (system: 0)
2018-03-01 17:04:54.9790 -0800  0xfd29 1024 0x0 4216 AccessibilitySettingsLoader: AXSettingsLoader told to start
2018-03-01 17:04:54.9967 -0800  0xfd29 1024 0x0 4216 UIAccessibility: Starting accessibility server
2018-03-01 17:04:55.1193 -0800  0xfd29 1024 0x0 4216 UIAccessibility: Started AXRuntime server: 0
2018-03-01 17:04:55.1239 -0800  0xfd29 1024 0x0 4216 UIAccessibility: (null): Loading synchronously
2018-03-01 17:04:55.1262 -0800  0xfd29 1024 0x0 4216 UIAccessibility: Main bundle finished loading: load type: 0 - is system app server: 0 (<UIApplication: 0x113d0adb0>)
2018-03-01 17:04:55.2735 -0800  0xfd3c 1024 0x0 4216 FrontBoardServices: [FBSScene] [fr.ourcompany.ournewappname] Created client agent: <UIApplicationSceneClientAgent: 0x1c401d120>
2018-03-01 17:04:55.2742 -0800  0xfd3c 1024 0x0 4216 FrontBoardServices: [FBSScene] [fr.ourcompany.ournewappname - AirPlay] Created client agent: <UIApplicationSceneClientAgent: 0x1c001d3f0>
2018-03-01 17:04:55.7238 -0800  0xfd29 1024 0x0 4216 UIKit: View did appear: <SplashScreenController: 0x113d6d690> 1
2018-03-01 17:04:55.7253 -0800  0xfd29 1024 0x0 4216 UIAccessibility: Did post notification. notification:  (1001) error:0 data:(null)
2018-03-01 17:04:55.7334 -0800  0xfd29 1024 0x0 4216 UIAccessibility: Did post notification. notification:  (4002) error:0 data:{
    controllerClass = SplashScreenController;
    event = ViewDidAppear;
}

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   ournewappname                   0x0000000100b3e9d8 0x100640000 + 5237208
1   ournewappname                   0x000000010065339c 0x100640000 + 78748
2   ournewappname                   0x0000000100653740 0x100640000 + 79680
3   CoreFoundation                  0x00000001811c513c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 20 (CFNotificationCenter.c:661)
4   CoreFoundation                  0x00000001811c46dc _CFXRegistrationPost + 420 (CFNotificationCenter.c:163)
5   CoreFoundation                  0x00000001811c4440 ___CFXNotificationPost_block_invoke + 60 (CFNotificationCenter.c:1060)
6   CoreFoundation                  0x0000000181241e24 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1408 (CFXNotificationRegistrar.m:163)
7   CoreFoundation                  0x00000001810fad60 _CFXNotificationPost + 380 (CFNotificationCenter.c:1057)
8   Foundation                      0x0000000181b27348 -[NSNotificationCenter postNotificationName:object:userInfo:] + 68 (NSNotification.m:543)
9   UIKit                           0x000000018ad28a20 +[UIScreen _FBSDisplayConfigurationConnected:andNotify:] + 280 (UIScreen.m:599)
10  UIKit                           0x000000018aa51060 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 292 (UIApplication.m:3094)
11  UIKit                           0x000000018ae66dbc -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 364 (UIApplicationSceneClientAgent.m:41)
12  FrontBoardServices              0x00000001838f61f0 -[FBSSceneImpl _didCreateWithTransitionContext:completion:] + 364 (FBSSceneImpl.m:460)
13  FrontBoardServices              0x00000001838feaf8 __56-[FBSWorkspace client:handleCreateScene:withCompletion:]_block_invoke_2 + 224 (FBSWorkspace.m:606)
14  libdispatch.dylib               0x0000000180bb2a14 _dispatch_client_callout + 16 (object.m:502)
15  libdispatch.dylib               0x0000000180bba200 _dispatch_block_invoke_direct$VARIANT$mp + 288 (queue.c:3025)
16  FrontBoardServices              0x000000018392a7f8 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 36 (FBSSerialQueue.m:164)
17  FrontBoardServices              0x000000018392a49c -[FBSSerialQueue _performNext] + 404 (FBSSerialQueue.m:196)
18  FrontBoardServices              0x000000018392aa38 -[FBSSerialQueue _performNextFromRunLoopSource] + 56 (FBSSerialQueue.m:232)
19  CoreFoundation                  0x00000001811db77c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24 (CFRunLoop.c:1982)
20  CoreFoundation                  0x00000001811db6fc __CFRunLoopDoSource0 + 88 (CFRunLoop.c:2017)
21  CoreFoundation                  0x00000001811daf84 __CFRunLoopDoSources0 + 204 (CFRunLoop.c:2053)
22  CoreFoundation                  0x00000001811d8b5c __CFRunLoopRun + 1048 (CFRunLoop.c:2920)
23  CoreFoundation                  0x00000001810f8c58 CFRunLoopRunSpecific + 436 (CFRunLoop.c:3245)
24  GraphicsServices                0x0000000182fa4f84 GSEventRunModal + 100 (GSEvent.c:2245)
25  UIKit                           0x000000018a8515c4 UIApplicationMain + 236 (UIApplication.m:3956)
26  ournewappname                   0x0000000100645980 0x100640000 + 22912
27  libdyld.dylib                   0x0000000180c1856c start + 4

Thread 1:
0   libsystem_pthread.dylib         0x0000000180e5ab68 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib         0x0000000180e5ab68 start_wqthread + 0

Thread 3 name:  Dispatch queue: com.apple.frontboardservices.workspace.client
Thread 3:
0   CoreFoundation                  0x00000001810f3d6c CFDataGetBytePtr + 88 (CFInternal.h:714)
1   Foundation                      0x0000000181b3296c bytesInEncoding + 200 (NSStringEncodings.m:155)
2   Foundation                      0x0000000181b3296c bytesInEncoding + 200 (NSStringEncodings.m:155)
3   CoreFoundation                  0x0000000181104f6c -[__NSCFString UTF8String] + 80 (CFObject.m:228)
4   BaseBoard                       0x0000000183703ee8 BSSerializeStringToXPCDictionaryWithKey + 44 (BSXPCSerialization.m:171)
5   BaseBoard                       0x0000000183703ce8 BSSerializeBSXPCEncodableObjectToXPCDictionary + 52 (BSXPCSerialization.m:86)
6   BaseBoard                       0x0000000183703ca4 BSCreateSerializedBSXPCEncodableObject + 56 (BSXPCSerialization.m:51)
7   BaseBoard                       0x0000000183703d88 BSSerializeBSXPCEncodableObjectToXPCDictionaryWithKey + 40 (BSXPCSerialization.m:59)
8   FrontBoardServices              0x00000001838f929c -[FBSWorkspaceSceneClientSettingsChangedEvent encodeWithXPCDictionary:] + 84 (FBSWorkspaceSceneClientSettingsChangedEvent.m:52)
9   BaseBoard                       0x0000000183703ce8 BSSerializeBSXPCEncodableObjectToXPCDictionary + 52 (BSXPCSerialization.m:86)
10  BaseBoard                       0x0000000183703ca4 BSCreateSerializedBSXPCEncodableObject + 56 (BSXPCSerialization.m:51)
11  BaseBoard                       0x0000000183703d88 BSSerializeBSXPCEncodableObjectToXPCDictionaryWithKey + 40 (BSXPCSerialization.m:59)
12  BaseBoard                       0x0000000183720a30 +[BSXPCMessage messageWithPacker:] + 96 (BSXPCMessage.m:33)
13  BaseBoard                       0x000000018371db08 -[BSBaseXPCClient _sendMessage:withReplyHandler:waitForReply:waitDuration:] + 132 (BSBaseXPCClient.m:187)
14  FrontBoardServices              0x0000000183918710 -[FBSWorkspaceClient _queue_sendMessage:withEvent:withResponseEvent:ofType:] + 144 (FBSWorkspaceClient.m:300)
15  libdispatch.dylib               0x0000000180bb2a54 _dispatch_call_block_and_release + 24 (init.c:994)
16  libdispatch.dylib               0x0000000180bb2a14 _dispatch_client_callout + 16 (object.m:502)
17  libdispatch.dylib               0x0000000180bbc96c _dispatch_queue_serial_drain$VARIANT$mp + 528 (inline_internal.h:2500)
18  libdispatch.dylib               0x0000000180bbd2fc _dispatch_queue_invoke$VARIANT$mp + 340 (queue.c:5302)
19  libdispatch.dylib               0x0000000180bbdd20 _dispatch_root_queue_drain_deferred_wlh$VARIANT$mp + 404 (queue.c:5920)
20  libdispatch.dylib               0x0000000180bc603c _dispatch_workloop_worker_thread$VARIANT$mp + 644 (source.c:2529)
21  libsystem_pthread.dylib         0x0000000180e5af1c _pthread_wqthread + 932 (pthread.c:2207)
22  libsystem_pthread.dylib         0x0000000180e5ab6c start_wqthread + 4

Thread 4:
0   libsystem_pthread.dylib         0x0000000180e5ab68 start_wqthread + 0

Thread 5 name:  com.apple.uikit.eventfetch-thread
Thread 5:
0   libsystem_kernel.dylib          0x0000000180d27568 mach_msg_trap + 8
1   libsystem_kernel.dylib          0x0000000180d273e0 mach_msg + 72 (mach_msg.c:103)
2   CoreFoundation                  0x00000001811db108 __CFRunLoopServiceMachPort + 196 (CFRunLoop.c:2613)
3   CoreFoundation                  0x00000001811d8cd4 __CFRunLoopRun + 1424 (CFRunLoop.c:2969)
4   CoreFoundation                  0x00000001810f8c58 CFRunLoopRunSpecific + 436 (CFRunLoop.c:3245)
5   Foundation                      0x0000000181b2d594 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 304 (NSRunLoop.m:367)
6   Foundation                      0x0000000181b4c9ac -[NSRunLoop(NSRunLoop) runUntilDate:] + 96 (NSRunLoop.m:411)
7   UIKit                           0x000000018b3bb7a8 -[UIEventFetcher threadMain] + 136 (UIEventFetcher.m:437)
8   Foundation                      0x0000000181c2f0f4 __NSThread__start__ + 996 (NSThread.m:1181)
9   libsystem_pthread.dylib         0x0000000180e5c2b4 _pthread_body + 308 (pthread.c:740)
10  libsystem_pthread.dylib         0x0000000180e5c180 _pthread_start + 312 (pthread.c:799)
11  libsystem_pthread.dylib         0x0000000180e5ab74 thread_start + 4

Thread 6:
0   libsystem_pthread.dylib         0x0000000180e5ab68 start_wqthread + 0

Thread 7 name:  GC Finalizer
Thread 7:
0   libsystem_kernel.dylib          0x0000000180d480f0 __psynch_cvwait + 8
1   libsystem_pthread.dylib         0x0000000180e5ece4 _pthread_cond_wait$VARIANT$mp + 640 (pthread_cond.c:579)
2   ournewappname                   0x00000001012e86a8 0x100640000 + 13272744
3   ournewappname                   0x00000001012cd658 0x100640000 + 13162072
4   ournewappname                   0x00000001012e5400 0x100640000 + 13259776
5   ournewappname                   0x00000001012e8df0 0x100640000 + 13274608
6   libsystem_pthread.dylib         0x0000000180e5c2b4 _pthread_body + 308 (pthread.c:740)
7   libsystem_pthread.dylib         0x0000000180e5c180 _pthread_start + 312 (pthread.c:799)
8   libsystem_pthread.dylib         0x0000000180e5ab74 thread_start + 4

Thread 8 name:  BatchDeleteObjects
Thread 8:
0   libsystem_kernel.dylib          0x0000000180d275a4 semaphore_wait_trap + 8
1   libdispatch.dylib               0x0000000180bb4f04 _dispatch_sema4_wait$VARIANT$mp + 24 (lock.c:134)
2   libdispatch.dylib               0x0000000180bb58b4 _dispatch_semaphore_wait_slow + 140 (semaphore.c:143)
3   ournewappname                   0x0000000100d546b8 0x100640000 + 7423672
4   ournewappname                   0x0000000100cd40dc 0x100640000 + 6897884
5   ournewappname                   0x0000000100d53c8c 0x100640000 + 7421068
6   libsystem_pthread.dylib         0x0000000180e5c2b4 _pthread_body + 308 (pthread.c:740)
7   libsystem_pthread.dylib         0x0000000180e5c180 _pthread_start + 312 (pthread.c:799)
8   libsystem_pthread.dylib         0x0000000180e5ab74 thread_start + 4

Thread 9 name:  AsyncReadManager
Thread 9:
0   libsystem_kernel.dylib          0x0000000180d275a4 semaphore_wait_trap + 8
1   libdispatch.dylib               0x0000000180bb4f04 _dispatch_sema4_wait$VARIANT$mp + 24 (lock.c:134)
2   libdispatch.dylib               0x0000000180bb58b4 _dispatch_semaphore_wait_slow + 140 (semaphore.c:143)
3   ournewappname                   0x0000000100c3c530 0x100640000 + 6276400
4   ournewappname                   0x0000000100c3c074 0x100640000 + 6275188
5   ournewappname                   0x0000000100d53c8c 0x100640000 + 7421068
6   libsystem_pthread.dylib         0x0000000180e5c2b4 _pthread_body + 308 (pthread.c:740)
7   libsystem_pthread.dylib         0x0000000180e5c180 _pthread_start + 312 (pthread.c:799)
8   libsystem_pthread.dylib         0x0000000180e5ab74 thread_start + 4

Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000048   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000101f8b03c
    x4: 0x0000000000000010   x5: 0x0000000000000001   x6: 0x0000000000000000   x7: 0x0000000000000403
    x8: 0x0000000101f8fa40   x9: 0x0000000000000001  x10: 0x0000000101f8ad60  x11: 0x0000000113d15730
   x12: 0x0000000101f8adb8  x13: 0x0000000000000002  x14: 0x0000000113e01680  x15: 0x016b5c01016b5cc0
   x16: 0x0000000180e51c60  x17: 0x0000000181b31d38  x18: 0xfffffff01210d25c  x19: 0x0000000000000002
   x20: 0x000000016f7bdc38  x21: 0x0000000101f8a000  x22: 0x0000000000000002  x23: 0x0000000000000000
   x24: 0x0000000000000002  x25: 0x000000016f7bdc38  x26: 0x0000000000000001  x27: 0x00000001b2373650
   x28: 0x0000000000000001   fp: 0x000000016f7bdb60   lr: 0x0000000100b3e9d8
    sp: 0x000000016f7bd9f0   pc: 0x0000000100b3e9d8 cpsr: 0x60000000

由于我们无法重现崩溃，因此难以修复。在这个崩溃日志中有一些关于SplashScreenController的内容，所以万一我们删除了启动画面，并且还将Unity版本更改为2017.3.1并重新提交应用程序......

真的很感激任何帮助，也许我们在崩溃日志中遗漏了一些有用的信息？

Answer 1

我们遇到了同样的问题（同样的异常和应用商店拒绝）。我们遇到了这个似乎是罪魁祸首的Unity漏洞。

https://issuetracker.unity3d.com/issues/ios-11-build-crashes-on-remotear-unityupdatedisplaylist-when-launching-app-from-url-with-airplay-connected

当用户流式传输设备屏幕（AirPlay等）时，有一个错误导致了这次崩溃。我认为测试人员有时会使用AirPlay，导致崩溃，而开发人员没有看错。

幸运的是，这个错误已在Unity中得到纠正，并且已经被移植到几个Unity补丁版本中：

修正于：的 2018.1.0b1

向后移植到：的 2017.3.0p2 2017.2.1p2 2017.1.3p1

从2017.2.1更新到2017.2.1p2后，我们的应用程序被接受了。

Answer 2

上周五我们因为同样的原因拒绝了AR应用程序。我们将Unity 2017.3.0f3与原生Vuforia集成和Xcode 9.2结合使用;我们也使用原生分享。

我们从Apple收到的崩溃日志与您的@Jeff几乎相同;崩溃的线程上显示相同的异常类型和方法。

我会尝试降级到不同版本的Unity，然后分享我的结果。

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000088
VM Region Info: 0x88 is not in any region.  Bytes before following region: 4377919352
  REGION TYPE                      START - END             [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
  UNUSED SPACE AT START
--->  
  __TEXT                 0000000104f1c000-0000000104f20000 [   16K] r-x/r-x SM=COW  .../OurApp]

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
Triggered by Thread:  0

和

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   OurApp                      0x0000000105463334 0x104f1c000 + 5534516
1   OurApp                      0x0000000104f2f130 0x104f1c000 + 78128
2   OurApp                      0x0000000104f2f4d4 0x104f1c000 + 79060
3   CoreFoundation                  0x0000000184bd113c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 20 (CFNotificationCenter.c:661)
4   CoreFoundation                  0x0000000184bd06dc _CFXRegistrationPost + 420 (CFNotificationCenter.c:163)
5   CoreFoundation                  0x0000000184bd0440 ___CFXNotificationPost_block_invoke + 60 (CFNotificationCenter.c:1060)
6   CoreFoundation                  0x0000000184c4de24 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1408 (CFXNotificationRegistrar.m:163)
7   CoreFoundation                  0x0000000184b06d60 _CFXNotificationPost + 380 (CFNotificationCenter.c:1057)
8   Foundation                      0x0000000185533348 -[NSNotificationCenter postNotificationName:object:userInfo:] + 68 (NSNotification.m:543)
9   UIKit                           0x000000018e734a20 +[UIScreen _FBSDisplayConfigurationConnected:andNotify:] + 280 (UIScreen.m:599)
10  UIKit                           0x000000018e45d060 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 292 (UIApplication.m:3094)
11  UIKit                           0x000000018e872dbc -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] +                     364 (UIApplicationSceneClientAgent.m:41)
12  FrontBoardServices              0x00000001873021f0 -[FBSSceneImpl _didCreateWithTransitionContext:completion:] + 364 (FBSSceneImpl.m:460)
13  FrontBoardServices              0x000000018730aaf8 __56-[FBSWorkspace client:handleCreateScene:withCompletion:]_block_invoke_2 + 224 (FBSWorkspace.m:606)
14  libdispatch.dylib               0x00000001845bea14 _dispatch_client_callout + 16 (object.m:502)
15  libdispatch.dylib               0x00000001845c6200 _dispatch_block_invoke_direct$VARIANT$mp + 288 (queue.c:3025)
16  FrontBoardServices              0x00000001873367f8 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 36 (FBSSerialQueue.m:164)
17  FrontBoardServices              0x000000018733649c -[FBSSerialQueue _performNext] + 404 (FBSSerialQueue.m:196)
18  FrontBoardServices              0x0000000187336a38 -[FBSSerialQueue _performNextFromRunLoopSource] + 56 (FBSSerialQueue.m:232)
19  CoreFoundation                  0x0000000184be777c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24 (CFRunLoop.c:1982)
20  CoreFoundation                  0x0000000184be76fc __CFRunLoopDoSource0 + 88 (CFRunLoop.c:2017)
21  CoreFoundation                  0x0000000184be6f84 __CFRunLoopDoSources0 + 204 (CFRunLoop.c:2053)
22  CoreFoundation                  0x0000000184be4b5c __CFRunLoopRun + 1048 (CFRunLoop.c:2920)
23  CoreFoundation                  0x0000000184b04c58 CFRunLoopRunSpecific + 436 (CFRunLoop.c:3245)
24  GraphicsServices                0x00000001869b0f84 GSEventRunModal + 100 (GSEvent.c:2245)
25  UIKit                           0x000000018e25d5c4 UIApplicationMain + 236 (UIApplication.m:3956)
26  OurApp                      0x0000000104f21880 0x104f1c000 + 22656
27  libdyld.dylib                   0x000000018462456c start + 4

Answer 3

今天，App审核小组成员终于检查了我们的案例，并验证了我们的应用程序，尽管之前已将其标记为已拒绝。

该应用程序连续5次遭到拒绝，并且最后两次都没有崩溃记录。

我们在4天前联系了应用审核小组，使用此表单对申请拒绝提出申诉：https://developer.apple.com/contact/app-store/?topic=appeal

我认为Apple测试程序在很大程度上依赖于自动测试，在某些情况下，这是不可靠的，他们的＆＃34; bot＆＃34;拒绝我们的应用程序虽然它完美地工作。

Apple似乎忽视的是，我们花了不眠之夜尽一切可能找到解决方案，以便我们的客户按时申请......

我希望每个人都能解决这个问题，我只能建议你通过各种方式与苹果联系，让一个人看看你的应用程序。

Answer 4

自上周以来，我们也遭遇了因类似原因拒绝我们的申请。然后，我查看了@HidingGlass的帖子并应用了Unity的补丁。因此，我们的申请通过了Apple的审核。

我会分享结果。

拒绝：ver.2017.2.1f1
接受：ver.2017.2.1p2

Answer 5

有趣的是，我们在这里遇到了完全相同的问题。我们之前一直在发送Apple版本进行审核，并且他们都在他们的设备上工作（仅针对一些小问题拒绝），直到几天前。尽管他们在我们的测试设备上工作正常，但他们已经拒绝了我们的两个版本，因为它们已经崩溃了。

这有什么奇怪的，他们对我们提交的内容都有同样的看法：

＆＃34;在我们审核期间，您的应用在连接到IPv6网络的运行iOS 11.2.5的iPad或iPhone上崩溃了。＆＃34;

不仅如此，它们提供的崩溃日志也反映了与您相同的问题。

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000088 VM Region Info: 0x88 is not in any region.

目前，我们即将发送一个正在审核中的上一个版本，并看看他们对此有何看法。

Answer 6

正如我在你对你的问题的评论中提到的那样，我偶尔可以通过关闭我的iPhone 7上的wifi来重现本地崩溃。经过一些挖掘后我发现有人将此问题添加到Unity问题跟踪器中2月底，但似乎该问题的网页今天或昨天都无法访问。

问题跟踪器网页最初可在此处访问： https://issuetracker.unity3d.com/issues/unitywebrequest-ios-2017-dot-3-player-crashes-at-job-executeunitywebrequest-when-switching-to-airplane-mode

Google仍然将其缓存在此处： http://webcache.googleusercontent.com/search?q=cache:TcQczK0adjMJ:https://issuetracker.unity3d.com/issues/unitywebrequest-ios-2017-dot-3-player-crashes-at-job-executeunitywebrequest-when-switching-to-airplane-mode&num=1&hl=en&gl=us&strip=0&vwsrc=0

网页无法在缓存的网址上正确呈现，但我可以通过查看来源并将其保存到我的计算机上的HTML文件来查看该网页。以下是它的截图：

问题中的堆栈跟踪与我在本地重现问题时看到的一致。有趣的是，该问题的评论提到这导致使用Vuforia的应用程序崩溃。我不使用Vuforia，但显然我的堆栈中的其他内容（可能是GVR SDK）正在发送导致我崩溃的Web请求。

更新1：按照页面评论中的建议，我降级到Unity 2017.2.1f并发现崩溃不再发生。所以，我将提交我的应用程序的这个版本，看看会发生什么。正如你所说，你已经在使用那个版本的Unity，这可能与你遇到的问题不同。

更新2：我的应用更新刚刚获得Apple批准。

Answer 7

我只需要和我一起登录。＆＃34;自上周以来完全一样的问题。我们设法通过打开支持票来获得我们的一个应用程序，但我们回到了最新更新的拒绝。无法在许多设备上进行重复操作，iPhone X，8,7 Plus，6S Plus，6，SE。

我们在Unity 2017.3中使用Vuforia 7来购买此应用程序。

Answer 8

在我们的案例中，我们在1月份的最后几个应用程序更新中使用过Unity 5.6.3p4，并且很快被批准（从提交到批准不到1天）。然而，一周前，应用程序处于“In Review”状态3天，然后由于此处所述的崩溃问题而被拒绝，而我们没有更改Unity版本并且没有添加任何新版本外部框架 - 所以，通过阅读其他所有回复的内容，我怀疑Apple最近必须在他们的评测测试机器人中改变一些东西（比如开始使用AirPlay），由于休眠的Unity bug而引发了这些问题。

有趣的是，这个问题正在Unity问题跟踪器中得到积极讨论，Unity工程师刚刚在DisplayManager.mm代码中发布了一个变通方法，并且他们只是将修复程序向后移植到5.6.5p3： https://issuetracker.unity3d.com/issues/ios-11-build-crashes-on-remotear-unityupdatedisplaylist-when-launching-app-from-url-with-airplay-connected?page=1#comments

至于我们，我们升级到2017.1.3p2并重新提交，并再次遭到拒绝 - 但这一次有不同的崩溃报告：

Termination Description: SPRINGBOARD, scene-create watchdog transgression: com.ourComany.ourApp exhausted real (wall clock) time allowance of 10.00 seconds

这似乎是自昨天以来在这里讨论的一些全新问题：

https://forum.unity.com/threads/ios-crash-on-startup-unity-2017-1-3p2.521666/#post-3424784

无法重现iOS App Review团队崩溃。与Vuforia的Unity应用程序

8 个答案: