Hi,
I seem to be having problems when deploying an app to a physical device.
This is a new solution, so I'm not sure if this is due to the latest update
of MonoDevelop/Mono for Android.
I see this in the AndroidTools log file:
[2013-02-03 15:57:23.6] DEBUG: RunShellCommand: 015d2d3e5d13fa0b a
This looks to be a new error, as I'm unable to deploy a pre-existing app that
I had previously been able to compile and then deploy.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Failed-to-deploy-Internal-error-tp5712827p5712828.html
Sent from the Mono for Andr
On Feb 2, 2013, at 5:39 PM, technohead wrote:
> Hmm, not seeing the ability to set the log verbosity levels in MonoDevelop
> (OS X)/Preferences/Debugger.
It's in Preferences/Build:
http://docs.xamarin.com/Android/Guides/Deployment%2C_Testing%2C_and_Metrics/Diagnostics#Diagnostic_MSBuil
Looks like Google is no longer generating v1 API keys. Is there a v2 solution?
Thanks,
Narayan
From: monodroid-boun...@lists.ximian.com
[mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Tom Opgenorth
Sent: Friday, January 25, 2013 8:13 AM
To: Discussions related to Mono for Android
Subjec
Google will still provide keys until March 3rd, 2013:
https://developers.google.com/maps/documentation/android/v1/
There is a sample on using Google Maps for Android v2 here:
https://github.com/xamarin/monodroid-samples/tree/master/MapsAndLocationDemo_v2
Hope this helps...
On Sun, Feb 3, 2013 at
