Since iOS 13, Apple has changed the userAgent value and the WebKit browser is no longer identified as an iOS platform when using the JSBridge v10.0 or older. It causes that all calls to JSBridge functions fail on non-existing bridge instance.
This issue does not affect JSBridge v10.1 and newer where the more complex identification is used.
Solution is upgrading the JSBridge.js script to the latest version via NPM or from official GitHub repo.
Upgrading the script should not affect your solution and we keep in mind the backward compatibility on the first place.
If it's not possible to upgrade the script, we have applied the fix to older versions of JSBridge.js script and you can get exactly same version as you currently use in your solution from this repo with minimal change to source code.
Since iOS 13, Apple has changed the userAgent value and the WebKit browser is no longer identified as an iOS platform when using the JSBridge v10.0 or older. It causes that all calls to JSBridge functions fail on non-existing bridge instance.
This issue does not affect JSBridge v10.1 and newer where the more complex identification is used.
Solution is upgrading the JSBridge.js script to the latest version via NPM or from official GitHub repo.
Upgrading the script should not affect your solution and we keep in mind the backward compatibility on the first place.
If it's not possible to upgrade the script, we have applied the fix to older versions of JSBridge.js script and you can get exactly same version as you currently use in your solution from this repo with minimal change to source code.