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 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.
Takes photo OK (Motorola Moto G), photo file copied to specified directory and filename OK (from the Intent), but original file (with date and serial number as filename) remains in the DCIM/Camera folder. As if it copied rather than moved the file. Is it that the app needs specific permissions to move rather than copy the file? If there was a way to know the original path in DCIM/Camera, the app could delete it, but can't see where this would be exposed. Ideal fix (I think) would be to make the move work in the first place.
Closing this as the issue is probably an error with the way the picture is configured. This did not happen with me on my Nexus 5 using the default sample apps. Or, it may be a device-specific setting - all photos are saved regardless.
However, here are issues that may be interesting:
This repo is the new design of this Mobile API - we have deprecated the Mobile API in favor of various plugins (which have the equivalent/same API):
- Contacts: https://www.nuget.org/packages/Xam.Plugin.Contacts
- Geolocator: https://www.nuget.org/packages/Xam.Plugin.Geolocator
- Media: https://www.nuget.org/packages/Xam.Plugin.Media
This plugin model has several advantages:
- Each plugin is independent, and can be updated as such
- It is no longer an all-or-nothing package
- Plugins can be mixed/replaced with other plugins that offer similar features
Thanks for using the Mobile API, and we hope that the new plugin model will enable you to produce even better mobile apps.