Marc Rousavy
Marc Rousavy
> My understanding is Swift view code is running on different thread so it's ref methods should too. Threading is only implicit because of React Native. Nitro itself does not...
#736 solves this - if you create your `ArrayBuffer` on the native side, it's **owning** - and going through JS to native again won't lose that information from now on!
Update: I successfully made Swift `Promise` an `actor` in this PR: https://github.com/mrousavy/nitro/pull/756 This will have a **minor** performance hit for the sake of Thread-safety. There were no Threading issues with...
..did you read my review comments?
woah I haven't seen that before - don't know where a bad_weak_ptr can come from
can you run the app through Android Studio with a debugger attached to see where it exactly stops? I need a C++ stacktrace or line number to see where its...
Hm, I'm guessing this must be coming from `hybridRef` - specifically here, where we create a `shared_ptr` from the `jni::global_ref`: https://github.com/mrousavy/nitro/blob/6957f31e5f65594e6080f2bdb24a7d85ba5b0a2e/packages/react-native-nitro-image/nitrogen/generated/android/c%2B%2B/views/JHybridTestViewStateUpdater.cpp#L49-L50 Maybe `shared_from_this()` doesn't like being called from within different...
Can you try if this fixes your issue? https://github.com/mrousavy/nitro/pull/632
This was a hard one, but I think I finally fixed this in #803 :) pls lmk if this works