#22 and #23 were fixed in @featbit/js-client-sdk@4.2.15 — thank you! However, those fixes don't currently reach React Native / React users, because the dependency chain uses exact pins all the way down:
@featbit/react-native-sdk → @featbit/react-client-sdk: "4.2.9" (exact)@featbit/react-client-sdk@4.2.9 → @featbit/js-client-sdk: "4.2.9" (exact)- npm
@featbit/js-client-sdk latest: 4.2.15
Because both pins are exact (no ^), a fresh npm install @featbit/react-native-sdk resolves js-client-sdk@4.2.9, so the half-open-socket and reconnect-backoff fixes never load on mobile — exactly the platform where they matter most.
Reaching RN users requires a coordinated release:
react-client-sdk bumps its js-client-sdk dependency to 4.2.15 (or a ^4.2.x range) and publishes.react-native-sdk bumps its react-client-sdk dependency and publishes.
Filing this so the propagation isn't lost now that the upstream issues are closed. Happy to open the version-bump PRs if that's helpful.
#22 and #23 were fixed in
@featbit/js-client-sdk@4.2.15— thank you! However, those fixes don't currently reach React Native / React users, because the dependency chain uses exact pins all the way down:@featbit/react-native-sdk→@featbit/react-client-sdk:"4.2.9"(exact)@featbit/react-client-sdk@4.2.9→@featbit/js-client-sdk:"4.2.9"(exact)@featbit/js-client-sdklatest:4.2.15Because both pins are exact (no
^), a freshnpm install @featbit/react-native-sdkresolvesjs-client-sdk@4.2.9, so the half-open-socket and reconnect-backoff fixes never load on mobile — exactly the platform where they matter most.Reaching RN users requires a coordinated release:
react-client-sdkbumps itsjs-client-sdkdependency to4.2.15(or a^4.2.xrange) and publishes.react-native-sdkbumps itsreact-client-sdkdependency and publishes.Filing this so the propagation isn't lost now that the upstream issues are closed. Happy to open the version-bump PRs if that's helpful.