Bug 15712 - UIVideoEditorController requires VideoPath assigned: change constructor?
Summary: UIVideoEditorController requires VideoPath assigned: change constructor?
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.9.5.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-10-25 14:42 UTC by Larry O'Brien
Modified: 2013-10-25 14:54 UTC (History)
1 user (show)

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

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 Larry O'Brien 2013-10-25 14:42:56 UTC
If the `VideoPath` is not set, the class `UIVideoEditorController` throws:

MonoTouch.Foundation.MonoTouchException: Objective-C exception thrown.  Name: NSInvalidArgumentException Reason: videoCameraImage must be either video or audio
  at (wrapper managed-to-native) MonoTouch.ObjCRuntime.Messaging:void_objc_msgSend (intptr,intptr)

    var c = new UIVideoEditorController();
    //c.VideoPath = "medium.m4v";
    window.RootViewController = c;

Should we remove / deprecate the default constructor and provide a ctor(String videoPath) ?
Comment 1 Larry O'Brien 2013-10-25 14:54:55 UTC
Well, I guess we probably don't want to enforce the assignment at the moment of initialization.