Bug 58850 - NSInternalInconsistencyException from AVCaptureSession
Summary: NSInternalInconsistencyException from AVCaptureSession
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 10.14 (d15-4)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2017-08-17 14:37 UTC by Ivan Herrera
Modified: 2017-08-17 15:19 UTC (History)
7 users (show)

Is this bug a regression?: ---
Last known good build:

Solution with storyboard (37.30 KB, application/zip)
2017-08-17 14:37 UTC, Ivan Herrera

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Ivan Herrera 2017-08-17 14:37:07 UTC
Created attachment 24275 [details]
Solution with storyboard

Message "Custom components are not being rendered because problems were detected" appears after loading storyboard. Also, some views are not being displayed correctly. Attaching solution code sample.

Log: https://gist.github.com/iherrera/97f743fcca76810df68ce21396a4f685
Env: https://gist.github.com/iherrera/037563ec3c03bf2e849c53b70bea6d8a
Comment 1 Alan McGovern 2017-08-17 14:48:41 UTC
I'm pretty sure this is just the user code doing something which doesn't work at design time.

iOS folks, does this mean anything to you? https://gist.github.com/iherrera/97f743fcca76810df68ce21396a4f685#file-gistfile1-txt-L491-L540

My guess is that the correct thing to do is make the control design-time aware and avoid doing asynchronous operation that crash: https://developer.xamarin.com/guides/ios/user_interface/designer/ios_designable_controls_overview/#Design_Mode
Comment 2 Rolf Bjarne Kvinge [MSFT] 2017-08-17 15:08:28 UTC
You're correct, the control is doing something it shouldn't do in design mode (capturing audio/video (with AVCaptureSession)).
Comment 3 Ivan Herrera 2017-08-17 15:14:18 UTC
Designer also takes an eternity to load the storyboard file when latest XI is installed
Comment 4 Jeffrey Stedfast 2017-08-17 15:19:20 UTC
I'm not getting the error you are seeing, but I think I am seeing some views not showing up properly.

Let me know if I am missing anything.

There are 4 screens, the first is a NagigationViewController which shows up correctly afaict.

The second is a camera view with a "Resume" button init. The problem in VS4M is that it has a white bg instead of black like Xcode shows it (not sure if this is a bug or just a stylistic difference).

The third controller should have a Play and Pause button in the lower left corner according to Xcode, but they do not show up in VS4M.

The forth controller should have a square cell in the upper left corner according to Xcode, but it also does not appear in VS4M.
Comment 5 Jeffrey Stedfast 2017-08-17 15:19:46 UTC
n/m, I guess Alan figured it out