You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a error when I try to start server in Android version, inside a project which has been packed into JAR. Error is related to access try to null point. More specifically,
Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid.
The same project works well, if it hasn't been packed into JAR. This issue is not related to assets, required files for OSVR Server, as required files are pushed into app directory manually.
The text was updated successfully, but these errors were encountered:
Could you describe what you mean by packing a project into the JAR? The current sample has the plugin and config files in the project's assets directory, which gets built into the application package as installed onto the device. At runtime, it then copies files from the package into the app's private data directory. If you are packaging up the plugins and config files in a different way (a separate JAR file, perhaps?), then you'll need to make sure you copy them into the data folder and set the CWD to that directory, as the sample does.
As I explained in email, implemented server-client uses JointClientKit and that functionality is a part of library. Sample applications that has dependency on library (in Android studio), works well, but once library exported as JAR file (library.jar) and applications are implemented using this .jar file gives error. Its a weird issue that I can't figure out.
There is a error when I try to start server in Android version, inside a project which has been packed into JAR. Error is related to access try to null point. More specifically,
Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid.
The same project works well, if it hasn't been packed into JAR. This issue is not related to assets, required files for OSVR Server, as required files are pushed into app directory manually.
The text was updated successfully, but these errors were encountered: