NativeScript / NativeScript/android
com.tns.Runtime.runWorker exception
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 563
- Forks
- 144
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 14
Description
Fatal Exception: com.tns.NativeScriptException: Cannot find runtime for id:1
at com.tns.Runtime.runWorker(Runtime.java)
at com.tns.Runtime.access$1500(Runtime.java:39)
at com.tns.Runtime$WorkerThread$1.run(Runtime.java:472)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:214)
at android.os.HandlerThread.run(HandlerThread.java:65)
nativescript: 6.2.2
tns-core-modules: 6.2.1
tns-android: 6.2.0
tns-ios: 6.2.0
I get this crash occasionally while developing with HMR.
Now, this crash is even showing up in production.
It's related to worker threads not loading as expected.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at com.tns.Runtime.runWorker in Runtime.java and inspect the worker-thread path associated with “Cannot find runtime for id:1.” Compare behavior across the listed NativeScript, tns-core-modules, tns-android, and tns-ios versions, reproducing it during HMR and in production-like execution. Done means worker threads load their runtime without this exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100