Update contents fail data integrity check

[tomauty]

Hi, hopefully this is just something I'm doing incorrectly. Lately I've had to deploy updates twice in a row to get them accepted. The first time I send one out, it always returns that I failed a data integrity check. This is the function I run to generate my release

/Users/tom/.nvm/versions/node/v4.2.1/bin/react-native bundle \
--reset-cache=true \
--entry-file=index.ios.js \
--platform=ios --dev=false \
--minify=true \
--bundle-output ./release/main.jsbundle \
--sourcemap-output ./release/main.map \
--assets-dest ./release

And then I follow up with

code-push release MyAppName ./release "*" --mandatory --deploymentName Staging

What other info might you need to help me out with this? :) Thanks

[tomauty]

Note that if I run that top command twice (without changing anything the second time) and do a second deploy, it will work! I would think they would have the same checksum. Not sure what's going on.

[lostintangent]

@tomauty Is it the "this release is identical to the existing one" message that you're seeing? If so, that may be due to React Native packager caching issues.

Have you tried using the new release-react command in the CodePush CLI? It will handle the bundling process for you and will also make sure to clear the packager cache (via rm -rf $TEMP/react-*) before hand. Using it, you could simply type code-push release-react MyApp ios -m -t "*" to achieve the same affect as your two scripts.

[tomauty]

Unfortunately no, it's this one:
The update contents failed the data integrity check.

I could try release-react, but my first command above should reset the packager cache anyway, I would think.

[tomauty]

Good to know that I can shorten this build process though!

[lostintangent]

@tomauty OK thanks for clarifying. We'll investigate this issue since you definitely shouldn't be seeing it. In the meantime, are you unblocked? It's just a pain to have to release twice? (I just want to make sure I know the severity of the issue)

[tomauty]

Yeah I don't mind releasing twice. If it helps, this also only happens when I'm updating from an existing codepush bundle. If I reinstall, I'll get the newest package without a second push.

[lostintangent]

OK cool, thanks for this detail @tomauty. We'll let you know the findings of investigating this issue.

[geof90]

@tomauty Can you inspect the "./release" folder for changes the second time u generate it using the react-native CLI? I have noticed that if you don't mkdir the "./release" folder first, sometimes the JS bundle doesn't appear or some assets go missing.

[tomauty]

Hmm I can do that. I definitely keep the release folder there for my whole development cycle, but it is still worth checking out, for sure.

[lostintangent]

@tomauty Were you ever able to try out @geof90's suggestion? I'd like to try to resolve this, and we haven't been able to repro it :/ Thanks again and sorry for this annoyance.

[tomauty]

Will be testing it now. In the past I've checked the release folder and it looked okay. I'll take a checksum too to be sure.

Edit - Failed integrity check the first time. Here's the checksum:
5f78678ff70af61d1997c3562e41dfe0
Obtained via find -s release -type f -exec md5sum {} \; | md5sum.

[tomauty]

Second release has a different checksum than the first, I wonder if my method is bad. Anyway, will keep posted.

[tomauty]

Second one did work. Also noted that the bundle size was much larger the second time around. Maybe I should be re-creating the release folder every time?

[tomauty]

First bundle had size 2300095 bytes, latter had 8865515. Sorry for spam, just reporting all possibly relevant info.