My AndroidManifest.xml is being ignored. I created it in the VS
dialogue, and the permissions are not being granted on my app. If I look
at the applications properties in Android, only INTERNET is granted.
http://schemas.android.com/apk/res/android";
android:installLocation="internalOnly" a
Our app appears to run ok on a Beta tester's Acer A500 honeycomb tablet
running OS 3.1. What problem areas should we look out for on Honeycomb
devices with apps compiled using Mono for Android 1.0.3?
Thanks...Andrew
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/A
Honeycomb can still run applications that targeted older versions of the
API. The problem is really just that Mono for Android doesn't currently have
bindings to the Honeycomb APIs, so you won't be able to take advantage of
anything specific to that in the current version.
On Sun, Sep 4, 2011 at 6
VS should have added this when it created the AndroidManifest.xml, but
something may have happened. Ensure you have this in your .csproj:
Properties\AndroidManifest.xml
Jonathan
On 9/4/2011 4:29 AM, Stuart Johnson wrote:
> My AndroidManifest.xml is being ignored. I created it in the VS
> dial
Thanks, thats fixed it. I added it under
On 04/09/11 15:56, Jonathan Pobst wrote:
> VS should have added this when it created the AndroidManifest.xml, but
> something may have happened. Ensure you have this in your .csproj:
>
> Properties\AndroidManifest.xml
>
> Jonathan
>
>
> On 9/4/2011 4:29
I'm getting this exception in VS:
[cid:image001.png@01CC6B41.ADF45920]
What can I do to be able to debug my app again?
Nicklas
<>___
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/mo
Ah..Ok, thanks Greg. Shouldn't be a problem for my app then.
Regards...Andrew
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Android-4-0-Ice-Cream-Sandwich-tp4765247p4768075.html
Sent from the Mono for Android mailing list archive at Nabble.com.
__
I've seen one other report of this, but it was not reproducible. If you
have a test case you can share that exhibits this issue, I can take a
stab at fixing it.
As for a workaround, I think your hitting an exception in your
application. Try running without debugging (Ctrl-F5) and see if you c
