Bug 29295 - ImageSource.FromStream not working on Windows platform
Summary: ImageSource.FromStream not working on Windows platform
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 1.4.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-04-22 03:35 UTC by pierrehenri
Modified: 2016-04-13 18:03 UTC (History)
3 users (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 pierrehenri 2015-04-22 03:35:43 UTC
This code works fine on iOS and Android 

image.Source = ImageSource.FromStream(() => new MemoryStream(imageAsBytes));

On Windows platform the image is not displayed (empty).

Comment 1 Stephane Delcroix 2015-05-27 07:18:52 UTC
Could you please attach a project exposing this issue on windows, and actually working on iOS or android ? From our tests, it works all right.

Please note that iOS, android and WP might not support the same image formats natively.
Comment 2 Samantha Houts [MSFT] 2016-04-13 18:03:30 UTC
Thank you for your bug report. As we have not received the information requested, we cannot properly triage your bug and are marking it resolved.

Warm regards,
Xamarin Forms Team