[Windows] Fix for PickPhotosAsync throws exception if image is modified

[HarishwaranVijayakumar]

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!

Issue Details

• PickPhotosAsync throws an ObjectDisposedException when size or compression options are used.

Root Cause of the issue

• The method ApplyMetadataAsync in ImageProcessor.windows.cs returns the same stream that was passed in. However, on iOS and Android, it returns a new stream. After ApplyMetadataAsync completes, the old stream is disposed. On Android and iOS, this is fine because a new stream is returned, so disposing the old one has no effect. But on Windows, since the same stream is returned and then disposed, accessing it afterward causes an exception.

Description of Change

• Resource management improvement:
  • In ImageProcessor.shared.cs, updated the logic to only dispose outputStream if ApplyMetadataAsync returns a different stream, preventing unintended disposal on platforms (like Windows) where the same stream may be returned.

Issues Fixed

Fixes #32408

Tested the behaviour in the following platforms

• - Windows
• - Android
• - iOS
• - Mac

Output

Before	After
BeforeFix.mp4	AfterFix.mp4

[dotnet-policy-service]

Hey there @@HarishwaranVijayakumar! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[sheiksyedm]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

Pull request overview

This PR fixes an ObjectDisposedException in PickPhotosAsync on Windows when using image size or compression options. The root cause was that ApplyMetadataAsync returns the same stream on Windows (and other platforms in error paths), but the code was unconditionally disposing the stream after the method call, making it unusable.

Key Changes:

• Added a reference equality check before disposing outputStream after ApplyMetadataAsync
• This prevents disposing a stream that's still needed when the same stream instance is returned
• The fix applies to all platforms since they all can return the same stream in various scenarios