Menu

The signed map and the app that rolls itself back
πŸ“°

The signed map and the app that rolls itself back

DEV Community: reactnativeΒ·Warren de LeonΒ·21 days ago
#ISxwnnyS
#devtoreactnative#devto#dev#version#remote
Reading 0:00
15s threshold

πŸ“š React Native Module Federation series β€” read it in full on warrendeleon.com , where new parts land first.

Post 16 ended on the two problems it left open: "A remote that fell back is forgotten at the next launch, so a version that keeps failing fails again on every launch before its copy takes over. Remembering failures belongs with the other open problem: the map every binary trusts is still a plain text file anyone who can write to the bucket can change." Post 15 had said the second one in eight words: "The chunks are guarded; the map is naked."

This post closes both, and the series with them. The map gets a signature, a release counter and, on the device, a memory. A map the app cannot verify is refused. An older map served again is refused. And when a signed map names a version that fails to load on two launches, the third launch does not try it: that remote runs from the copy in the binary while the other stays on the content delivery network (CDN), and nobody is paged.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.