jacque006
All 4 comments
IMO, it should be. OTA is one of the USP of RN. And as far as i now, OTA bundle is essentially a zip file, so it can contain image assets and bytecode file.
kaushikwavhal
on 16 Jul 2019
We don't currently have an official strategy or integration with Code Push. However, nothing stops you from pushing your own pre-compiled bytecode files -- they essentially correspond 1:1 to JavaScript bundle files and can be loaded and managed in much the same way.
When given a file, Hermes will examine the header to determine whether it's JS or bytecode and load it accordingly, so you don't have to change anything about how the file is loaded or even which extension it has.
There is one significant caveat though: a bundle compiled with one version of Hermes will not run on a different version.
To maximize efficiency and productivity, we don't try to maintain forward or backward compatibility between versions. If you want to decouple app and code releases through code pushes, you should either stick to a specific version of Hermes, or have a strategy for pushing different bytecode to each applicable Hermes version.
(Specifically, the compiler encodes a bytecode version number in the bundle that the engine verifies on load).
None of this applies to standard apps that just include their bytecode in the APK. In this case you're free to upgrade Hermes at any time since the bytecode will always be compiled with the relevant version.
willholen
on 27 Jul 2019
@willholen Thanks for the update.
As i understand, An Hermes version upgrade can be treated in the same we as we treat a React-Native version upgrade in OTA. Backward and forward compatibility can work for the app versions which don't involve any change on the native side (Hermes or RN ).
kaushikwavhal
on 30 Jul 2019
Just a head up, I've created a PR to add Hermes support on CodePush CLI here, feel free to comment:
eggli
on 6 Aug 2019
Related issues
thymikee
路
6Comments
akrger
路
6Comments
benkane
路
5Comments
AMorgaut
路
6Comments
swabbass
路
3Comments
Most helpful comment
We don't currently have an official strategy or integration with Code Push. However, nothing stops you from pushing your own pre-compiled bytecode files -- they essentially correspond 1:1 to JavaScript bundle files and can be loaded and managed in much the same way.
When given a file, Hermes will examine the header to determine whether it's JS or bytecode and load it accordingly, so you don't have to change anything about how the file is loaded or even which extension it has.
There is one significant caveat though: a bundle compiled with one version of Hermes will not run on a different version.
To maximize efficiency and productivity, we don't try to maintain forward or backward compatibility between versions. If you want to decouple app and code releases through code pushes, you should either stick to a specific version of Hermes, or have a strategy for pushing different bytecode to each applicable Hermes version.
(Specifically, the compiler encodes a bytecode version number in the bundle that the engine verifies on load).
None of this applies to standard apps that just include their bytecode in the APK. In this case you're free to upgrade Hermes at any time since the bytecode will always be compiled with the relevant version.