Plamen Petkov
Plamen Petkov
@MrVonkey a workaround for the current issue could be solved with implementing the native class with the default constructor and accessing it through javascript. In other words, making a plugin.
Work on this issue/story will be resumed as soon as we gather enough feedback for the current state of the Workers
Hi @daveware-nv, we're going to be able to better assist you if you provide steps to reproduce, with the minimal code required or a small repo for us to check...
@daveware-nv > ...once I know what to look for The simplest way for me to explain what to look for. Consider this scenario in your code or in some native...
We haven't got a blog post about it because it's an experimental flag, and we're still contemplating on trying it out. We wanted to check out what kinds of problems...
@daveware-nv, did you manage to fix your issue or are you still trying to figure out where the problem is?
>And of course then there is nativescript-angular and nativescript-pro-ui, which I wouldn't know where to start looking, Both plugins are usable with the current version of the android runtime, but...
>Do you know what the timeframe (if any) for supporting markingMode: none for those plugins is? We've not settled on using `markingMode:none` by default yet, because we're still trying out...
Hi @yyankov thank you for your feedback. As I previously explained this error is caused by the fact your business logic encloses a native object, that's already collected. To put...
Closing due to lack of activity.