René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"False Update detection on first run","articleBody":"My CI server pushes every build to code-push (js) and other distr channels (for full ipa). I may have the following:\n- 1.0.0 (build 2) + code-push for js part only (1.0.2 version in package.json)\n- 1.0.0 (build 4) + code-push for js part only (1.0.4 version in package.json)\n- 1.1.0 (build 5) + code-push for js part only (1.1.5 version in package.json)\n- etc\n\nAfter installing new [full] build on the device, first run of the code-push sync() reports that there is an update. In reality, there is no need for the update, because full build already has latest js bundle.\n\ncode-push packages have automatically generated label (v1, v2 etc). If I can have extra metadata, say, version of the package, and control version matching on client side, I can avoid false positive update check of first run.\n\nAnother approach I see is to silently download update and inspect package.json in downloaded main.jsbundle (I don't know if it is possible). That may help avoiding false positive too.\n\nAny other ideas? May be I am missing something and using code-push not the way it was designed to work?\n\nThanks,\n~Andrey\n","author":{"url":"https://github.com/AndreyNikiforov","@type":"Person","name":"AndreyNikiforov"},"datePublished":"2016-01-25T17:51:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/122/code-push/issues/122"}