• EditorBugs
  • Update file integrity check failed

The latest version of spine has been working well on my computer. Today I have to import a spine project made with v3.8.75, so I tried to download and launch that old version of spine via the laucher. However, it failed to launch and I found this message in log: " Update file integrity check failed ... Spine\updates\3.8.75". What can I do to solve this problem? Thanks.
The attachment is the whole log file:

spine.log
2kB
Related Discussions
...

The issue you're encountering with the "Update file integrity check failed" message suggests that there might be a problem with the downloaded update file for Spine version 3.8.75. Here are a few steps you can take to resolve this issue:

  1. Re-download the Latest Launcher: Ensure you are using the latest Spine launcher. You can download it from your Spine license page. This can often resolve issues related to file integrity checks.

  2. Reboot Your Computer: Sometimes, other software might interfere with the update process. Rebooting your computer can help clear any such interference.

  3. Disable Antivirus Software: Temporarily disable any antivirus or firewall software that might be interfering with the download or integrity check process.

  4. Delete the Corrupted Update File: Navigate to the directory where the update file is stored (as indicated in the log: Spine\updates\3.8.75) and delete the corrupted file. Then, try downloading the update again through the Spine launcher.

  5. Check for Interfering Software: Ensure no other software is modifying or adding files to the Spine directory. This can include desktop environment metadata or other background processes.

If these steps do not resolve the issue, please provide the spine.log file for further analysis. You can find the log file in the following locations:

  • Windows: <user home folder>\Spine\spine.log
  • Mac: <user home folder>/Library/Application Support/Spine/spine.log
  • Linux: <user home folder>/.spine/spine.log

For more detailed troubleshooting, you can refer to the Spine Troubleshooting Guide.

That happens when Spine detects the update file doesn't match what it expects. Since you have the latest launcher and Spine just downloaded the 3.8.75 update file, it should be right.

Are you running Spine in a VM? Spine supports Apple M1 natively. For updates < 4.0 they use the old launcher (called "legacy" in the log) and that may not handle being run in a VM correctly.

  • ywlqjc ответили на это сообщение.
  • ywlqjc оценил это.

    Nate Thank you. Simply changing to Mac Apple Silicon version of spine solved my problem. It seems VM was indeed the cause.