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.
When you click Project -> Publish Android Application
I always have to re-locate my Key Store file every time I publish my Android Application.
This is mainly because the export location of the Apk file is in a different place to the keystore file, which can easily happen.
I always have to choose the location for the keystore file.
I always have to choose the location of the export
Desired and sensible behaviour:
For any given project where the apk file has been exported before, remember the path to the keystore, and remember the path to the export location, and keep in mind, these can be different.
I know this may not sound like an important thing to do, but if you have many projects, exporting the apk files can be additional tedium that could easily be avoided with those tiny fixes from your side.
Fast approaching the one year anniversary for this bug / feature request! :D
It's got a couple months to go - plenty of time to plan its birthday party.
Great, should we get some cake? I reckon so :)
Dear Xamarim: this is a productivity killer. Instead of working on next cool new feature, please consider working on this enhancement. Will save all of us a lot of time. I use Google Play for Betas, so I am hitting this frequently.
I agree with t9mike when he says "Instead of working on next cool new feature" .. we don't really need the cross platform API, for example, but we do need the core stuff to work really well - and some areas, like the debugger on OSX, are going backwards not forwards.
I think this can be closed, as it can easily be achieved using a python script that makes use of xbuild.
Although I do recommend you to add some info about this in your documentation, it wasn't too easy to get going with it!
We will be introducing an updated workflow for publishing which addresses this issue in XS 5.9