-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
Expose resolvePath to JavaScript #426
Conversation
Bundling and snapshotting android application requires a way to resolve a relative module path to an absolute one so expose runtime resolvePath method.
I have a question 😄 It looks to me that |
💚 |
If we want this to work the modules should be present in the package. If we don't want to include them in the package we should then include the package.json files in the bundle and create another runtime method that doesn't rely on File in order to retrieve the path. |
The better approach would be to retrieve the absolute path of a module during bundling, so I am closing this one |
I'm receiving the following error (#149) with this PR:
|
This happens when a JNI local ref is not deleted after it's used.
You generate strings as a JNI local ref, without releasing them, so I might suggest either releasing them with env->DeleteLocalRef(jniStrObj), or making them global, with env.newGlobalRef(jniStrObj), if you need them for the whole duration of the program. |
@KristinaKoeva better yet you can use JniLocalRef class like so: |
Bundling and snapshotting android application requires a way to resolve a relative module path to an absolute one so expose runtime resolvePath method.