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.
Created attachment 3057 [details]
So I was really excited to see that on the new BB10 platform that you can repackage the apk to a bar file to make it compatible with the platform:
This potentially means that Xamarin, without having to do very much, has the ability to run on an additional platform!
However in the conversion process there were many problems. I tried to convert a brand new M4A project (the sample one with a single button and event) to the bar format and I was attacked by a lot of issues in the conversion process. The log is attached.
Will it ever be possible for M4A to produce apk files that are able to be converted?
Very interesting stuff Dylan. Thanks for the feature request. Unfortunately, this is not currently slated for implementation / compatibility fixing.
Stay subscribed to this bug to receive any updates.
Xamarin will not be able to support this until Blackberry removes their restrictions on the inclusion of native code:
> Unsupported Software Features
> * Apps that utilize native code bundled into their APK file
My gut feeling is that this isn't easily solvable: BlackBerry uses QNX, not Linux, and BlackBerry uses it's own libc and dynamic library support, etc. I would be surprised if it were easily possible for BlackBerry to load arm-linux-androideabi ELF binaries as-is, plus fully implement JNI support (and whatever else is needed to support Java `native` methods...).
Regardless, there's nothing Xamarin/Mono for Android can do on this front until BlackBerry supports native code in Android apps.
An alternative approach would be to skip Android support, and go directly to BlackBerry support: