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.
I'm using google maps component in android (GooglePlayServicesFroyo).
The days I have a problem in using the release mode, already researched on
various websites, I followed all the steps and gives error when run. In
debug mode, it works perfectly.
From what I could see, the problem occurs because of the signing of the
app, I've created another key in "Google API Console" with "keystore"
signing the app, changed the "AndroidManifest.xml" and still does not work.
Could help me, I'm using VS2012 with windows 8 and android Xamarin is
I am sending herewith the project that the error is occurring.
When running, need to get on the "REVENDAS" to view the map.
In release mode, the app is crashing with "UNHANDLED EXCEPTION: System.InvalidCastException: Cannot cast from source type to destination type" when I try to load the map view.
Created attachment 5069 [details]
Description make is sound like an Android issue.
This could be a variation on Bug #15177.
@goldberger: Please retest when XA 4.8.3 is stable and an updated GooglePlayServicesFroyo component is on the component store.
Is there any estimate of when version 4.8.3 will be stable? I am waiting for this fix to publish the app for a client.
4.8.3 has been stable for ages. Please re-test.
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!