Open EgorBo opened 6 years ago
I like this idea.
Maybe we can implement a check in AVCaptureDevice.RequestAccessForMediaTypeAsync
that is linked away in release builds, like we do for UIButton.VerifyIsUIButton:
There are too many API that trigger permissions crashes, they are not documented and they vary (mostly additions) with every new release. Also our release cycle makes it quite hard to keep up even with the ones that gets reported. It's a race that is lost :(
Now they do have something in common, along with other issues - they cause a SIGABRT
. We should build our customized mono to replace
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
with a different message like:
=================================================================
A crash (SIGABRT) occurred while executing native code.
The simulator or device logs often provide additional details about the crash condition.
Please consult https://ms.net/redirect-to-something-we-control for more details.
=================================================================
That link can :
Steps to Reproduce
ViewDidLoad
:Expected Behavior
Some user friendly message telling user that he forgot to add a permission to his plist. In this case it's
NSCameraUsageDescription
Actual Behavior
iOS Device:
iOS Simulator (at least it notifies user):
Environment
iPhone X iOS 12