You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case a user installs a new JS bundle from a QR Code, but the version of the native application being used is not compatible in some way with these changes (for example if the native application binary is on RN60 but the JS bundle contains code running on RN61 only) LiveBundle could be smart enough to detect this incompatibility in some way (#19) and instead of warning the user or blocking installation, LiveBundle could know which corresponding native binary is aligned on these dependencies and offer the user to download/install this app binary prior to installing the JS bundle. For this to work, LiveBundle should be aware of native code incompatibilities (tackled by #19) but also should ideally be aware of the native binaries themselves so that it can download the right one (#102).
The text was updated successfully, but these errors were encountered:
In case a user installs a new JS bundle from a QR Code, but the version of the native application being used is not compatible in some way with these changes (for example if the native application binary is on RN60 but the JS bundle contains code running on RN61 only) LiveBundle could be smart enough to detect this incompatibility in some way (#19) and instead of warning the user or blocking installation, LiveBundle could know which corresponding native binary is aligned on these dependencies and offer the user to download/install this app binary prior to installing the JS bundle. For this to work, LiveBundle should be aware of native code incompatibilities (tackled by #19) but also should ideally be aware of the native binaries themselves so that it can download the right one (#102).
The text was updated successfully, but these errors were encountered: