I have an app which fetches some large sound files via On Demand Resource. One of my development devices began reporting the following error (after previously having loaded the tag successfully):
This device previously loaded the ODR data for the given tag and other devices are able to access the ODR tag without issues. There haven’t been any changes to the ODR related application code, nor to the resources which are hosted on an HTTP server for use in the development environment. After a re-install, this device started reporting the Code 4 error anytime beginAccessingResources() is called.
I believe I can fix the development device with the problem by uninstalling/reinstalling the app. However, I’m concerned that this may happen to a user in production and it is not reasonable for me to advise users to re-install the app if they encounter this.
Is there a way to programmatically prompt the ODR system to reset its data for the tags in question? Are there other ways to work around this Code 4 error in production without uninstalling the app?
Thanks!
Tim
Code Block Error Domain=SZExtractorErrorDomain Code=4 "Hash mismatch for chunk containing offset 0: expected 342058fc4bee7355f9670c99a797d1b1, got 936843a70e005b6768798d0619ae927a" UserInfo={NSLocalizedDescription=Hash mismatch for chunk containing offset 0: expected 342058fc4bee7355f9670c99a797d1b1, got 936843a70e005b6768798d0619ae927a, SZExtractorActualHashValueErrorKey=936843a70e005b6768798d0619ae927a, SZExtractorFileOffsetErrorKey=0, SZExtractorSourceFileLineErrorKey=474, SZExtractorFunctionNameErrorKey=-[StreamingUnzipState _checkHashForOffset:], SZExtractorHashChunkIndexErrorKey=0}
This device previously loaded the ODR data for the given tag and other devices are able to access the ODR tag without issues. There haven’t been any changes to the ODR related application code, nor to the resources which are hosted on an HTTP server for use in the development environment. After a re-install, this device started reporting the Code 4 error anytime beginAccessingResources() is called.
I believe I can fix the development device with the problem by uninstalling/reinstalling the app. However, I’m concerned that this may happen to a user in production and it is not reasonable for me to advise users to re-install the app if they encounter this.
Is there a way to programmatically prompt the ODR system to reset its data for the tags in question? Are there other ways to work around this Code 4 error in production without uninstalling the app?
Thanks!
Tim