Shiva Prasad

@bundyo Starting off from where you pointed, I've boiled it down to this https://gist.github.com/shiv19/1d027194e8d1107c5be20b6382b9b450 you can run this function off of the loaded event on the action bar. Setting the...

@bundyo can you give us any ETA for this please? :)

Interesting idea. So we could technically also add new localisation strings on the fly. Instead of using the switch case, we could do something like this, ```js let value; while(splits.length)...

@darind We're not using any custom workers in the app. But there is only 1 plugin in our app that uses workers, nativescript-particle plugin. It has 2 workers. I'm attaching...

This is the crash I get during development ``` An uncaught Exception occurred on "W1: ./ffa39720cb93dc65b0d3.worker.js" thread. Cannot find runtime for id:2 StackTrace: at com.tns.Runtime.runWorker(Native Method) at com.tns.Runtime.access$1500(Runtime.java:39) at com.tns.Runtime$WorkerThread$1.run(Runtime.java:472)...

I started getting this ever since I started using {N} 6.2

I've made a release with --no-hmr, will report here if I see that crash go away

@darind There is only one plugin in our app that uses workers. Nativescript-particle. It has 2 workers. Attaching the latest version that we use. [nativescript-particle-2.2.4.tgz.zip](https://github.com/NativeScript/android-runtime/files/3929843/nativescript-particle-2.2.4.tgz.zip) It looks like the app...

Sorry, I forgot to leave an update here. The issue still persists in production. Building with `--no-hmr` did not help.

I tried going back to an older version of dev-webpack (1.2.1), that did not help. The crash still occurs.