The PictureChooser plugin provides implementations of:

public interface IMvxPictureChooserTask
    void ChoosePictureFromLibrary(int maxPixelDimension, int percentQuality, Action<Stream> pictureAvailable,
                                  Action assumeCancelled);

    void TakePicture(int maxPixelDimension, int percentQuality, Action<Stream> pictureAvailable,
                     Action assumeCancelled);

Note: ChoosePictureFromLibrary and TakePicture must be called from the UI Thread on iOS.

This is available on Android, iOS and Windows Uwp.

This interface is designed for single use only - i.e. each time you require a picture you should request a new IMvxPictureChooserTask instance.

The interface can be used as:

var task = Mvx.IoCProvider.Resolve<IMvxPictureChooserTask>();
task.ChoosePictureFromLibrary(500, 90,
stream => {
    // use the stream
    // expect the stream to be disposed after immediately this method returns.
() => {
    // perform any cancelled operation

Note: Using this interface well on Android is very difficult.

The reason for this is because of Android’s Activity lifecycle. The Android lifecycle means that the image that may be returned to a different View and ViewModel than the one that requested it. This is partly because camera apps generally use a lot of RAM (raw camera images are large files) - so while th camera app is capturing you image, then Android may look to free up additional RAM by killing your app’s Activity.

If you want to use this IMvxPictureChooserTask effectively and reliably on Android then you really need to call this API via a service class, to use Messaging to pass the returned message back to a ViewModel and to implement ‘tombstoning’ support for that ViewModel.

There is a simple demo for IMvxPictureChooserTask in PictureTaking - however, this simple demo doesn’t currently show this full Android technique.

Note: On Windows Phone 8.0, an additional implementation is available:

public interface IMvxCombinedPictureChooserTask
    void ChooseOrTakePicture(int maxPixelDimension, int percentQuality, Action<Stream> pictureAvailable,
                             Action assumeCancelled);

Client code can test for the availability of this interface using:

var isAvailable = Mvx.IoCProvider.CanResolve<IMvxCombinedPictureChooserTask>();


IMvxCombinedPictureChooserTask combined;
var isAvailable = Mvx.IoCProvider.TryResolve(out combined);

Finally, the PictureChooser plugin also provides an “InMemoryImage” ValueConverter - MvxInMemoryImageValueConverter. This value converter allows images to be decoded from byte arrays for use on-screen.

The “InMemoryImage” ValueConverter can be seen in use in the PictureTaking sample - see

Windows Phone 8.1

Windows Phone 8.1 and Windows 8.1 API hasn’t converged entirely and there are differences in how pictures are handled. If you want to choose pictures from the gallery, you need to implement a EventHandler on your Page, which listens to Activated events. This is due to the picture data is returned on that event on Windows Phone 8.1.

Hence in your constructor of your page add:

var view = CoreApplication.GetCurrentView();
view.Activated += ViewOnActivated;

The ViewOnActivated EventHandler will look something like this:

private void ViewOnActivated(CoreApplicationView sender, IActivatedEventArgs args)
    var continuationArgs = args as FileOpenPickerContinuationEventArgs;
    if (continuationArgs == null) return;


The ContinueFileOpenPicker() method in the ViewModel simply calls the same method on the IMvxPictureChooserTask:

public void ContinueFilePicker(object args)
    if (_currentChooserTask == null) return;


If you don’t want to expose this method in your ViewModel, the alternative is to pass a message using IMvxMessenger instead.