NativeScript / NativeScript/android

Crash: No implementation found for void com.tns.AssetExtractor.extractAssets

Open
#1,225 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
563
Forks
144
Avg merge
10h 46m
Merged PRs (30d)
14

Description

Environment

  • CLI: 4.2.1
  • Cross-platform modules: 4.2.0
  • Android Runtime: 4.2.0

Describe the bug

We got several crash reports mostly occuring on Huawei devices running Android 9.0 where the app crashes on startup because of a missing AssetExtractor implementation (which seems pretty weird)

Any ideas what's happening there and how to resolve it?

Stack trace:

12-07 15:44:02.932 10130 12663 12663 E No implementation found for void com.tns.AssetExtractor.extractAssets(java.lang.String, java.lang.String, java.lang.String, boolean) (tried Java_com_tns_AssetExtractor_extractAssets and Java_com_tns_AssetExtractor_extractAssets__Ljava_lang_String_2Ljava_lang_String_2Ljava_lang_String_2Z)
12-07 15:44:02.933 10130 12663 12663 D AndroidRuntime: Shutting down VM
--------- beginning of crash
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: FATAL EXCEPTION: main
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: Process: ***.***.control, PID: 12663
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: java.lang.UnsatisfiedLinkError: No implementation found for void com.tns.AssetExtractor.extractAssets(java.lang.String, java.lang.String, java.lang.String, boolean) (tried Java_com_tns_AssetExtractor_extractAssets and Java_com_tns_AssetExtractor_extractAssets__Ljava_lang_String_2Ljava_lang_String_2Ljava_lang_String_2Z)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at com.tns.AssetExtractor.extractAssets(Native Method)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at com.tns.AssetExtractor.extractAssets(Unknown Source:38)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at com.tns.RuntimeHelper.initRuntime(Unknown Source:111)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at com.tns.NativeScriptApplication.onCreate(Unknown Source:19)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1162)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6535)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at android.app.ActivityThread.access$1900(ActivityThread.java:267)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1957)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:109)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:207)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:7439)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
12-07 15:44:02.934 10130 12663 12663 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:958)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the AssetExtractor.extractAssets entry point and follow its call from RuntimeHelper.initRuntime during NativeScriptApplication.onCreate. Compare the reported JNI method signature with the available implementation and reproduce startup on the affected Android configuration. Done means startup no longer raises UnsatisfiedLinkError for extractAssets.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp, java
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.