Very weird indeed. I've only seen that error reported once so far, so it's definitely not happening often. Is it possible that also having the trial library installed on the device could cause that to happen?
On Thu, Jul 21, 2011 at 4:21 PM, Jonathan Pryor <j...@xamarin.com> wrote: > On Jul 21, 2011, at 1:40 PM, Greg Shackles wrote: > > I actually saw this error reported once in the Android Market for my app > as well, which it claimed came from a Nexus One (though I have also seen the > app successfully installed to a coworker's N1). I checked my APK and > lib\armeabi\libmonodroid.so is in there. > > Interesting. > > I can think of only two reasons that libmonodroid.so wouldn't be loaded: > > 1. It's not there (e.g. it's present for an ABI that the device can't > run). > 2. libmonodroid.so is loaded, but JNI_OnLoad() returns 0. This shouldn't > happen [0]. > > If the same package is successfully installed and runs on one device, it > makes no sense to me that it would fail on another. That would require > additional exploration. :-( > > - Jon > > [0] Unless you somehow get the trial libmonodroid.so onto hardware… > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid >
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
