Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 44984 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 17849 [details]
In UWP, you are unable to edit a local image file (name, delete or anything) after it has been loaded into the Xamarin.Forms application. This is still the case even if the image has been disposed of in the application. A native UWP project can load an image, remove the image, dispose the image, and then you can edit the file while the project is still running.
Attached repo case is a basic Forms sample where after running, you won't be able to change anything about the local file while the app is running.
Steps to reproduce:
1. Copy "testPhoto.jpeg" to the local directory of the application.
2. Run application to load image
3. Unable to delete/replace/rename photo file via File Explorer after app loads. Message: "the file is open in TestXF_UWP.UWP"
Able to delete/replace/rename photo file via File Explorer after app loads
Unable to delete/replace/rename photo file via File Explorer after app loads. Message: "the file is open in TestXF_UWP.UWP"
Any news here? I noticed the same Problem a couple of times in Xamarin Forms UWP projects.
Such a basic functionality should really work without any problems.
This problem is still occurring with Xamarin.Forms version 18.104.22.168779, has there been any progress resolving this issue?