Kirill Rodichev
Kirill Rodichev
Was able to fix by implementing `InvalidateCacheOnDestroy` as it's done in `react-native-mmkv`
@Sangkwun, yes, I've mentioned previously how I fixed the issue > Was able to fix by implementing InvalidateCacheOnDestroy as it's done in react-native-mmkv
@Sangkwun, I didn't modify mmkv, I patched quick-crypto so that MGLTypedArray implementa cache invalidation as it's done in latest mmkv version
@robertsLando I plan to test this patch for `onMessage` in production for a while and will update you on whether it resolves the issue. ``` diff --git a/node_modules/mqtt/build/lib/connect/ws.js b/node_modules/mqtt/build/lib/connect/ws.js index...
@robertsLando it didn't work. I still get EOF in production after the fix. Will try to figure out why
@sanduluca could you explain why did you stick to `proxy._writableState.ended` and not `proxy._readableState.ended`. from what I understand, `proxy._writableState.ended` indicates that the writable side is ended, but `proxy.push()` is an operation...
@robertsLando I made some experiments that show that we better use `readable` here ``` import { Duplex } from 'stream'; class MyDuplex extends Duplex { constructor() { super(); this.data =...