-
Notifications
You must be signed in to change notification settings - Fork 48
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
How can i export this application to aar library #5
Comments
Can you run this application directly (not exported as aar library) on your testing device successfully without the "UnsatisfiedLinkError" you mention? |
Application run directly in my phone without problem. I asked same question on JavaCpp repo. It seems *.so file related. But i have no idea how to import them correctly. |
I am not very famillar with android and java development.
If you have time can you look into it. Please. I am pulling all my hairs here I created aar from with this method simple library works. |
I used this app to see copied libs. if this app working right then *.so files seems copied. Is it possible that *.so files are copied and not being referenced? |
The problem is this application currently not working on sdk version 23 or above. (See #3 ) |
Thank you It was sdk version. My app worked. Looking forward to sdk 23 support. |
You can checkout 'sdk-23-plus' branch to try it on SDK 23 or above now. |
Thank you I will do that. |
I want to use
FFmpegRecordActivity
from Nativescript.For that I have to export application to aar library and call
FFmpegRecordActivity
class from javascript via Intent.I did that part It worked.
But after
FFmpegRecordActivity
is displayed it breaks with this error.It seems not nativescript problem. Because same thing happened when i import aar from another android studio application.
camera, external storage permissions are given and on for application
I did the trick from bytedeco/javacv#133 : moved *.so files to "app/src/main/jniLibs/armeabi-v7a" and "app/src/main/jniLibs/armeabi" folders and it seems not working
The text was updated successfully, but these errors were encountered: