-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems when run on cordova-android@7 #8
Comments
Looks like the shared object libraries didn't get deployed to the Android project. |
I updated the Cordova CLI to the latest version (8.1.2) and re-added the cordova-android@7 but the situation is the same. |
OK, I'll take a look. Maybe the SO's are not getting deployed into the right place for cordova-android@7 since I updated the platform version... |
The Android libs path has changed in cordova-android@7 - the above commit updates this plugin to use the new path so it should now run OK with cordova-android@7 |
Yeah now work! Thank you! |
I think this needs a major version increase (breaking change), right? |
@brodybits yeah, in a "real" plugin it would - cordova-android@7 has caused some really breaking changes. But since this one is just an example plugin and isn't published to npm, the semantic versioning is redundant so I won't bother here. BTW nice idea though to workaround it by wrapping all the .so files in a .jar |
One more thing that is not clear to me. I would like to add my .c and .h files and the general flow would be:
|
yep, but if you're doing this with the plugin in-place inside an app project (i.e.
Otherwise, if your plugin lives outside of the your app directory, you can do:
|
Okay thank you |
I just raised apache/cordova-docs#902 to get this documented properly. |
FYI I just raised apache/cordova-android#547 to deal with the large number of plugins not working on cordova-android@7. |
@brodybits thanks, I have had compatibility problems reported against [email protected] which appears to make some breaking changes, e.g dpa99c/cordova-android-support-gradle-release#32 (comment) I've worked around that particular issue (change in deployment location of Gradle files) in a new plugin version. As for this example plugin, it's now the new version 18 of the Android NDK which is causing me issues - although I've updated the plugin to deploy the so files to the new location used by cordova-android@7 the C implementations of the JNI interface functions are not being found at runtime. Hopefully it's just a question of updating the C function signatures. |
hi,
I'm trying to make the test project work with [email protected] but when I run on Android device, the test app starts but outputs only deviceready.
In the Android Studio Logcat this warn comes back:
I do not know if this is the problem but before the support at cordova-android@7, the test app worked with cordova-platform@6.
Thanks
The text was updated successfully, but these errors were encountered: