@kontextso/sdk-react-native 3.0.8-rc.0 → 3.0.8

package/dist/index.js

@@ -492,7 +492,7 @@ var import_react_native3 = require("react-native");
 var import_react_native_device_info = __toESM(require("react-native-device-info"));
 
 // package.json
-var version = "3.0.7";
+var version = "3.0.8";
 
 // src/NativeRNKontext.ts
 var import_react_native2 = require("react-native");

package/dist/index.mjs

@@ -464,7 +464,7 @@ import { Appearance, Dimensions, PixelRatio, Platform } from "react-native";
 import DeviceInfo from "react-native-device-info";
 
 // package.json
-var version = "3.0.7";
+var version = "3.0.8";
 
 // src/NativeRNKontext.ts
 import { TurboModuleRegistry } from "react-native";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kontextso/sdk-react-native",
-  "version": "3.0.8-rc.0",
+  "version": "3.0.8",
   "description": "Kontext SDK for React Native",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",

package/src/formats/Format.tsx

@@ -296,6 +296,13 @@ const Format = ({ code, messageId, wrapper, onEvent, ...otherParams }: FormatPro
     }
   }
 
+  /*
+  * Fix for Android issue in Saylo.
+  * When the iframe is loaded, the onLoad event is sometimes called two or more times. 
+  * When these events fire too quickly, the init-iframe response from the server gets discarded. 
+  * As a result, our SDK doesn’t send the update-iframe event back to the server, and the stream never starts.
+  * This fix will send the update-iframe event even if the init-iframe isn’t received. 
+  */
   useEffect(() => {
     const interval = setInterval(() => {
       if (messageStatusRef.current === MessageStatus.None) {