BlackBerry Runtime for Android Apps repackaging

Unity Engine
,
1

Has anyone successfully repackaged a Unity-built Android app for Blackberry’s upcoming Playbook OS which contains their Android App Player? I used BlackBerry’s online compatibility tester, which just analyzes an apk file that you upload. My apps all failed the compatibility test. The tool spat out this message - “the following features are not supported by BlackBerry Runtime for Android Apps”:

uses-access-native com.unity3d.player.PlayerPrefs
uses-access-native com.unity3d.player.UnityJavaRunnable
uses-access-native com.unity3d.player.UnityPlayer
uses-access-native com.unity3d.player.WWW
uses-access-native org.fmod.FMODAudioDevice

I have a few apps that don’t even contain code that access PlayerPrefs or WWW, yet they have still failed. It seems these dependencies get built into the apk regardless of whether they’re used or not. They’re not in the manifest file, and I have searched everywhere in my project directory for these strings, but I can’t find them. Does anyone know how to omit them from an apk build? Does anyone know any other workaround?

2

Since Unity uses the NDK to build native code, and the Blackberry just has a modified Dalvik VM, you won’t get it to work at all.

Notice your error messages? ‘uses-access-native’

An Android app that can run on the new Blackberry system needs to be written purely in Java, no native code at all. A Unity Android project is probably 99% native code.

It’s the exact same reason why you can’t build for GoogleTV.