Xcode 8.2.1 (8C1002): unable to open view debugger in Xcode

Originator:whakkee
Number:rdar://30205240 Date Originated:26-Jan-2017 12:47 PM
Status:Closed (duplicate) Resolved:
Product:Developer Tools Product Version:Xcode 8.2.1 (8C1002)
Classification:Other Bug Reproducible:Unable
 
Summary:
Tried to open view debugger, after selecting a tab on the UITabBar in the running app, and nothing seemed to happen

Console log had following message text: 
```
Error:    Unable to capture view hierarchy.
Details:  No plist data for fetching view hierarchy.
Method:   -[DBGAbstractViewDescriber handleFetchedViewInfo:fetchError:resultHandler:]
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
```

Steps to Reproduce:
click on view debugger icon in Xcode while app was running

Expected Results:
expected to see the view debugger

Actual Results:
no view debugger, error message instead

Regression:
have not seen this before, will update this ticket if I see it again

Notes:
was using a simulator at iOS 10.2 (14C89) using Xcode 8.2.1 (8C1002)

Comments

Response Jun 7:

The original report on your issue has been closed recently. Please note that you will not be able to directly view the original report in order to keep its information confidential.

Response Feb 3:


Engineering has provided the following feedback regarding this issue:

Thanks for your report! If this happens again while Xcode is in this failed state, please run the following command in Xcode’s console:

image list

…and see if it includes libViewDebuggerSupport.dylib (or attach the output) and update this report with your findings.


Request: if anyone here encounters this and has more info, please file a duplicate with this info, and comment here if you want to be really nice ;-)


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!