Error installing boost Verification checksum was incorrect #843

wswebcreation · 2023-12-31T10:17:02Z

I'm developing a Mobile app with React Native (0.73.1) and for building the app I need to install the pods. The pods contains installing boos, see this file.

I get the following error

Installing boost (1.83.0)

[!] Error installing boost
Verification checksum was incorrect, expected 6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e, got 5e89103d9b70bba5c91a794126b169cb67654be2051f90cf7c22ba6893ede0ff

When I check this site I see the checksum should be 6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e

When I do this on my Mac

curl -sL https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2 | shasum -a 256

5e89103d9b70bba5c91a794126b169cb67654be2051f90cf7c22ba6893ede0ff  -

I get a different checksum

Please let me know what I need to provide more to debug this

The text was updated successfully, but these errors were encountered:

RahulSingh225 · 2023-12-31T10:30:47Z

I'm developing a Mobile app with React Native (0.73.1) and for building the app I need to install the pods. The pods contains installing boos, see this file.

I get the following error
Installing boost (1.83.0)

[!] Error installing boost
Verification checksum was incorrect, expected 6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e, got 5e89103d9b70bba5c91a794126b169cb67654be2051f90cf7c22ba6893ede0ff
When I check this site I see the checksum should be 6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e

When I do this on my Mac
curl -sL https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2 | shasum -a 256

5e89103d9b70bba5c91a794126b169cb67654be2051f90cf7c22ba6893ede0ff  -
I get a different checksum

Please let me know what I need to provide more to debug this

Facing the same issue on M1 machine

vinpro24 · 2023-12-31T10:50:58Z

move to node_modules/react-native/third-party-podspecs.
Only change line
spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2',
:sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }
to
spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.83.0/boost_1_83_0.tar.bz2',
:sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

Maybe jfrog close their server

codeion · 2023-12-31T10:51:09Z

I have the same issue with React Native 0.72.7

Error installing boost
Verification checksum was incorrect, expected f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41, got 5e89103d9b70bba5c91a794126b169cb67654be2051f90cf7c22ba6893ede0ff

boost version 1.76.0

tecmusti · 2023-12-31T11:11:35Z

Just replace 83 with 76 and 6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e with f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41

#843 (comment)

I have the same issue with React Native 0.72.7

Error installing boost Verification checksum was incorrect, expected f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41, got 5e89103d9b70bba5c91a794126b169cb67654be2051f90cf7c22ba6893ede0ff

boost version 1.76.0

wswebcreation · 2023-12-31T12:27:42Z

Changing the checksum without knowing what happened isn’t a good solution. The checksum ensures the integrity and authenticity of your downloaded file, protecting against corrupted, incomplete, or maliciously altered files.
If you bypass the checksum verification, you risk introducing security vulnerabilities, stability issues, or subtle bugs in your application. These can be challenging to diagnose and may compromise your application or user data.

So there’s a reason why they use checksums and it's up to you all if you want to skip it 😅

tecmusti · 2023-12-31T12:34:37Z

Changing the checksum without knowing what happened doesn’t feel like a good solution. There’s a reason why they use checksums 😅

We are not changing the checksum. Original link is broken, just replacing it with sourceforge link.

wswebcreation · 2023-12-31T12:59:54Z

Ok, created a simple patch for this for RN 0.73.1, but everyone could do this

Install patch-package:

npm install --save-dev patch-package postinstall-postinstall

Modify boost.podspec:

change

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.83.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2',
                  :sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

  # Pinning to the same version as React.podspec.
  spec.platforms = min_supported_versions
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

to

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.83.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  # Patched due to issue https://github.com/boostorg/boost/issues/843
  spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.83.0/boost_1_83_0.tar.bz2',
                  :sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

  # Pinning to the same version as React.podspec.
  spec.platforms = min_supported_versions
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

Create a Patch:
- Run npx patch-package react-native to create a patch file based on your changes. This command generates a patch file in a directory called patches/.
Apply the Patch Automatically:
- Modify your package.json to apply the patch after installation. Add the following to your scripts section:
```
"scripts": {
  "postinstall": "patch-package"
}
```
- Now, whenever you run npm install, patch-package will automatically apply the patch to the boost.podspec file.

ronenempathy · 2023-12-31T13:41:47Z

facing the same issue with react-native 0.68.1.
any workaround for this?

wswebcreation · 2023-12-31T13:53:07Z

facing the same issue with react-native 0.68.1. any workaround for this?

Yes:

Go to node_modules/react-native/third-party-podspecs from the root of your project
check the boost.podspec for the version you need to use
check https://sourceforge.net/projects/boost/files/boost/ for the link of the file you need to have
get the checksum
Follow the steps from Error installing boost Verification checksum was incorrect #843 (comment)

ronenempathy · 2023-12-31T16:31:42Z

@wswebcreation since we are not pushing node_modules, is there any other ways to overcome this. this issue interrupts our CI as well.

wswebcreation · 2023-12-31T16:45:56Z

@ronenempathy

You are not creating a new module, you are creating a patch in your project that will be installed when you do the npm i

The steps mentioned above create the patch, here's how it looks like in my case

gregavola · 2023-12-31T16:57:11Z

What about for build systems like AppCenter, where node_modules are created at build time?

dafilmorais · 2023-12-31T16:58:17Z

Doesn't work. It just hangs "installing boost (1.76.0)"
Using sourceforge

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.76.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.76.0/boost_1_76_0.tar.bz2',
                  :sha256 => 'f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41' }

  # Pinning to the same version as React.podspec.
  spec.platforms = { :ios => '11.0' }
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

wswebcreation · 2023-12-31T17:01:04Z

What about for build systems like AppCenter, where node_modules are created at build time?

What do you mean?

wswebcreation · 2023-12-31T17:01:26Z

Doesn't work. It just hangs "installing boost (1.76.0)" Using sourceforge

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.76.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.76.0/boost_1_76_0.tar.bz2',
                  :sha256 => 'f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41' }

  # Pinning to the same version as React.podspec.
  spec.platforms = { :ios => '11.0' }
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

Sorry, can't help with that

sarunmrzn · 2023-12-31T17:03:48Z

Doesn't work. It just hangs "installing boost (1.76.0)" Using sourceforge

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.76.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.76.0/boost_1_76_0.tar.bz2',
                  :sha256 => 'f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41' }

  # Pinning to the same version as React.podspec.
  spec.platforms = { :ios => '11.0' }
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

Try running with verbose, pod install --verbose. Boost is 100+ MB ish depending on your connection.

gregavola · 2023-12-31T17:04:18Z

What about for build systems like AppCenter, where node_modules are created at build time?

What do you mean?

When AppCenter does a build, it generates does an yarn install to pull in everything in node_modules so editing these files locally, won't help the build process. Is there a way to override this on yarn install it pulls the correct url?

dafilmorais · 2023-12-31T17:07:38Z

Doesn't work. It just hangs "installing boost (1.76.0)" Using sourceforge

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.76.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.76.0/boost_1_76_0.tar.bz2',
                  :sha256 => 'f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41' }

  # Pinning to the same version as React.podspec.
  spec.platforms = { :ios => '11.0' }
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

Try running with verbose, pod install --verbose. Boost is 100+ MB ish depending on your connection.

Huh, looks like it is downloading. Just really slow. Thanks for the tip.
Jfrog links are dead, should be up again later sometime hopefully.

twercedev · 2023-12-31T18:29:06Z

@wswebcreation

Ok, created a simple patch for this for RN 0.73.1, but everyone could do this

Install patch-package:

npm install --save-dev patch-package postinstall-postinstall

Modify boost.podspec:

change

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.83.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2',
                  :sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

  # Pinning to the same version as React.podspec.
  spec.platforms = min_supported_versions
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

to

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.83.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  # Patched due to issue https://github.com/boostorg/boost/issues/843
  spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.83.0/boost_1_83_0.tar.bz2',
                  :sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

  # Pinning to the same version as React.podspec.
  spec.platforms = min_supported_versions
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

Create a Patch:
- Run npx patch-package react-native to create a patch file based on your changes. This command generates a patch file in a directory called patches/.
Apply the Patch Automatically:
- Modify your package.json to apply the patch after installation. Add the following to your scripts section:
```
"scripts": {
  "postinstall": "patch-package"
}
```
- Now, whenever you run npm install, patch-package will automatically apply the patch to the boost.podspec file.

@wswebcreation Thanks this works for me.

tecmusti · 2023-12-31T18:53:31Z

What about for build systems like AppCenter, where node_modules are created at build time?

What do you mean?

When AppCenter does a build, it generates does an yarn install to pull in everything in node_modules so editing these files locally, won't help the build process. Is there a way to override this on yarn install it pulls the correct url?

Try creating patch on your local computer and upload generated patch then modify package.json file to apply patches. This should work.

The jfrog.io account is currently disabled; see boostorg/boost#843

ali-sao · 2023-12-31T22:35:10Z

Who else is facing incredible slowness in jFrog? it took almost 45 minutes to install boost

Harisene · 2024-01-01T06:17:01Z

Who else is facing incredible slowness in jFrog? it took almost 45 minutes to install boost

same here

Harisene · 2024-01-01T06:19:43Z

What about for build systems like AppCenter, where node_modules are created at build time?

What do you mean?

When AppCenter does a build, it generates does an yarn install to pull in everything in node_modules so editing these files locally, won't help the build process. Is there a way to override this on yarn install it pulls the correct url?

Follow these steps to create a patch. #843 (comment)

Now when running yarn install the patch will be applied in the App Center.

mina4gerges · 2024-01-01T08:01:19Z

is it safe to change from https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2 to https://sourceforge.net/projects/boost/files/boost/1.83.0/boost_1_83_0.tar.bz2 ?

agrittiwari · 2024-01-01T08:22:49Z

Implemented the changes suggested as Suggested above, but it really didn't solve the problem. Made a patch of it, it doesn't solve the upstream problem, but crashes the pod install, somehow.

⚠️  Something went wrong running `pod install` in the `ios` directory.
Command `pod install` failed.
└─ Cause: Failed to load 'boost' podspec: 
[!] Invalid `boost.podspec` file: undefined local variable or method `min_supported_versions' for Pod:Module.

 #  from /Users/agrittiwari/wishup/client-app/node_modules/react-native/third-party-podspecs/boost.podspec:17
 #  -------------------------------------------
 #    # Pinning to the same version as React.podspec.
 >    spec.platforms = min_supported_versions
 #    spec.requires_arc = false
 #  -------------------------------------------


pod install --repo-update --ansi exited with non-zero code: 1

sdarwin · 2025-01-01T14:38:59Z

Hi @gregoripolak ,

The url is now:

https://archives.boost.io/
https://archives.boost.io/release/1.87.0/source/boost_1_87_0.tar.bz2

JFrog was donating bandwidth. After years, they have requested we switch to another service, to mitigate costs.

userdocs · 2025-01-01T14:53:33Z

The official URL is still jfrog here: https://www.boost.org/users/download/

The URL that was changed to https://archives.boost.io/ the last time this happened, now changed back to jfrog

edited for clarity:

sdarwin · 2025-01-01T14:59:25Z

@userdocs very interesting! Previous versions (1.86.0 etc) switched to the new download link. This needs to be fixed.

userdocs · 2025-01-01T15:05:36Z

@sdarwin yeah, I rephrased my comment The download page itself does not link to https://archives.boost.io/ nor the newer github latest assets.

That info could avoid non packaged boost related issues when jfrog shutdown last night.

Akifcan · 2025-01-01T19:47:59Z

@sdarwin yeah, I rephrased my comment The download page itself does not link to https://archives.boost.io/ nor the newer github latest assets.

That info could avoid non packaged boost related issues when jfrog shutdown last night.

Thank you this is work for me:

[root]/node_modules/react-native/third-party-podspecs/boost.podspec
spec.source = { :http => 'https://archives.boost.io/release/1.76.0/source/boost_1_76_0.tar.bz2',

line: 13
react native version: 0.71.11

jpieper · 2025-01-04T22:49:57Z

Hi @gregoripolak ,

The url is now:

https://archives.boost.io/ https://archives.boost.io/release/1.87.0/source/boost_1_87_0.tar.bz2

JFrog was donating bandwidth. After years, they have requested we switch to another service, to mitigate costs.

Any chance you could get JFrog to do a DNS forward to the new location? That should be pretty cheap and would keep many things working.

jtvargas · 2025-01-06T16:56:43Z

ok, so why on local pod install works without issues and then in my CI is not working ? I don't understand that 🤔

genesiscz · 2025-01-06T17:09:30Z

ok, so why on local pod install works without issues and then in my CI is not working ? I don't understand that 🤔

Because you have the package cached and is not required to re-download. CI is probably uncached

genesiscz · 2025-01-06T17:33:41Z

My patch file loosk like:

diff --git a/third-party-podspecs/boost.podspec b/third-party-podspecs/boost.podspec
index 3d9331c95d1217682a0b820a0d9440fdff074ae0..bbbb7380e51a12d1b2994c8ab8e8f682c5e6d83d 100644
--- a/third-party-podspecs/boost.podspec
+++ b/third-party-podspecs/boost.podspec
@@ -10,7 +10,7 @@ Pod::Spec.new do |spec|
   spec.homepage = 'http://www.boost.org'
   spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
   spec.authors = 'Rene Rivera'
-  spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.bz2',
+  spec.source = { :http => 'https://archives.boost.io/release/1.76.0/source/boost_1_76_0.tar.bz2',
                   :sha256 => 'f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41' }
 
   # Pinning to the same version as React.podspec.

into patches/[email protected] (or your own version)

jtvargas · 2025-01-06T17:36:19Z

is there another solution instead of the patch-package ? 👀 I would not like to do the patch-package

EnginKoyuncu · 2025-01-07T09:10:52Z

Ok, created a simple patch for this for RN 0.73.1, but everyone could do this

Install patch-package:
npm install --save-dev patch-package postinstall-postinstall

Modify boost.podspec:

change

Copyright (c) Meta Platforms, Inc. and affiliates.

This source code is licensed under the MIT license found in the

LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
spec.name = 'boost'
spec.version = '1.83.0'
spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
spec.homepage = 'http://www.boost.org'
spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
spec.authors = 'Rene Rivera'
spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2',
:sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

Pinning to the same version as React.podspec.

spec.platforms = min_supported_versions
spec.requires_arc = false

spec.module_name = 'boost'
spec.header_dir = 'boost'
spec.preserve_path = 'boost'
end
to

Copyright (c) Meta Platforms, Inc. and affiliates.

This source code is licensed under the MIT license found in the

LICENSE file in the root directory of this source tree.

Pod::Spec.new do |spec|
spec.name = 'boost'
spec.version = '1.83.0'
spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
spec.homepage = 'http://www.boost.org'
spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
spec.authors = 'Rene Rivera'

Patched due to issue #843

spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.83.0/boost_1_83_0.tar.bz2',
:sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

Pinning to the same version as React.podspec.

spec.platforms = min_supported_versions
spec.requires_arc = false

spec.module_name = 'boost'
spec.header_dir = 'boost'
spec.preserve_path = 'boost'
end
3. Create a Patch:

Run npx patch-package react-native to create a patch file based on your changes. This command generates a patch file in a directory called patches/.

Apply the Patch Automatically:

Modify your package.json to apply the patch after installation. Add the following to your scripts section:
"scripts": {
"postinstall": "patch-package"
}

Now, whenever you run npm install, patch-package will automatically apply the patch to the boost.podspec file.

Thanks for the fix! Anyone using 'App Center', follow these steps: Commit the file 'patches/react-native+0.72.6.patch' to your branch and let 'App Center' do the work. Just to be sure, after running 'yarn install' or 'npm i' locally, verify that you’ve got this applied.

Lazar4o · 2025-01-07T10:27:50Z

Could someone explain to me how this error appears out of nowhere? It seems that no one on my team is experiencing this issue.

sdarwin · 2025-01-07T11:46:40Z

@Lazar4o

It seems that no one on my team is experiencing this issue.

Great.

Could someone explain to me how this error appears out of nowhere?

The boost download was hosted on JFrog until December 31, 2024 when the service ended. Therefore the problem "appeared out of nowhere" on Jan 1, 2025.

Although not completely out of nowhere. the switch was announced in the mailing list, in github issues, and boost.org has pointed to the new download links for 6 months.

meramsey · 2025-01-15T15:01:15Z

for anyone else having issues still i stumbled onto easier fix for Podfile vs patch-package approach might be worth trying if not able to upgrade yet

#996 (comment)

JFrog is no longer offering webspace to Boost. They used to do this, but this is costing them a lot. Boost now offers their own in-house URL to download archives. See: - boostorg/boost#843 (comment) - boostorg/website#900 P.S. while this isn't breaking for the builds, as this is cached. This can result in breaking builds later, if the Dockerfile were to change.

JFrog is no longer used by Boost, as they were donating space and bandwidth. This have become too much of a cost. See: - boostorg/boost#843 (comment) - boostorg/website#900

edouard-claude · 2025-01-20T12:19:50Z

Fixed
https://www.boost.org/users/history/version_1_76_0.html

Pod::Spec.new do |spec|
  spec.name = 'boost'
  spec.version = '1.76.0'
  spec.license = { :type => 'Boost Software License', :file => "LICENSE_1_0.txt" }
  spec.homepage = 'http://www.boost.org'
  spec.summary = 'Boost provides free peer-reviewed portable C++ source libraries.'
  spec.authors = 'Rene Rivera'
  spec.source = { :http => 'https://archives.boost.io/release/1.76.0/source/boost_1_76_0.tar.bz2',
                  :sha256 => 'f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41' }

  # Pinning to the same version as React.podspec.
  spec.platforms = { :ios => '11.0' }
  spec.requires_arc = false

  spec.module_name = 'boost'
  spec.header_dir = 'boost'
  spec.preserve_path = 'boost'
end

misaelriojasftf · 2025-01-22T10:13:20Z

Errors

move to node_modules/react-native/third-party-podspecs. Only change line spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2', :sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' } to spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.83.0/boost_1_83_0.tar.bz2', :sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

Maybe jfrog close their server

In my case updating the version didn't work. it throw an error

[Hermes] Using the release tarball from Maven Central
[!] CocoaPods could not find compatible versions for pod "boost":
  In Podfile:
    RCT-Folly (from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`) was resolved to 2021.07.22.00, which depends on
      boost

    React-jsi (from `../node_modules/react-native/ReactCommon/jsi`) was resolved to 0.72.7, which depends on
      boost (= 1.76.0)

    boost (from `../node_modules/react-native/third-party-podspecs/boost.podspec`)

By trying to understand the error it quite obviously the checksum doesn't match and even if I force it to match it throws another error

Solution

use a patch and change the url of the boost file. It looks someone updated the frog link somehow not sure but even forcing to the actual checksum it still throws error like file is not correct format

so go here https://www.boost.org/users/history/ where you can find all the version. find the one you need and check the checksum

in my case this was the file link and this was the checksum and interesting is the checksum did match with the legacy one I got initially from react native

just paste the link instead of the frog one and it works!

wswebcreation mentioned this issue Dec 31, 2023

[Error installing boost] Verification checksum was incorrect, expected facebook/react-native#42110

Closed

kimyoungjae96 mentioned this issue Dec 31, 2023

Pod install error verification checksum was incorrect at boost (1.83.0) facebook/react-native#42109

Closed

amandeepmittal mentioned this issue Dec 31, 2023

pod install fails due to invalid verification checksum when I tried to run in iOS expo/expo#26178

Closed

rz-vastdata mentioned this issue Dec 31, 2023

Running scripts /setup-centos8.sh fails due to missing Boost dependency facebookincubator/velox#8207

Closed

mbunkus added a commit to mbunkus/org.bunkus.mkvtoolnix-gui that referenced this issue Dec 31, 2023

bump Boost to 1.84.0 & use SourceForge mirror

0894220

The jfrog.io account is currently disabled; see boostorg/boost#843

yard2010 mentioned this issue Jan 2, 2025

Verification checksum was incorrect #996

Open

This was referenced Jan 7, 2025

Build failing to install package bcgov/bc-wallet-mobile#2335

Closed

feat: update base bifold packages bcgov/bc-wallet-mobile#2334

Merged

tequdev mentioned this issue Jan 10, 2025

Update boost link for build-full.sh Xahau/xahaud#421

Merged

12 tasks

chrisnojima mentioned this issue Jan 10, 2025

patch boost issue in podlock keybase/client#28293

Merged

This was referenced Jan 10, 2025

Updating Boost download location LLNL/saltatlas#85

Merged

Hotfix/boost url LLNL/ygm#273

Merged

jian4on mentioned this issue Jan 10, 2025

feat: Change network status check feature in NetInfo, disable/enable mediator check and provide new method to check isInternetReachable openwallet-foundation/bifold-wallet#1390

Merged

5 tasks

a1re1 mentioned this issue Jan 12, 2025

Update boost package source microsoft/react-native-macos#2332

Open

c0mtru1se mentioned this issue Jan 12, 2025

[testapp] Update testapp RN-related dependencies to latest wultra/react-native-powerauth-mobile-sdk#221

Open

MatthiasVC pushed a commit to emweb/winstng that referenced this issue Jan 16, 2025

Update Boost download URL

adc4523

JFrog is no longer used by Boost, as they were donating space and bandwidth. This have become too much of a cost. See: - boostorg/boost#843 (comment) - boostorg/website#900

pagoru mentioned this issue Jan 24, 2025

fix concurrency build fail openhotel/openhotel#563

Open

Error installing boost Verification checksum was incorrect #843

Error installing boost Verification checksum was incorrect #843

Comments

wswebcreation commented Dec 31, 2023

RahulSingh225 commented Dec 31, 2023

vinpro24 commented Dec 31, 2023

codeion commented Dec 31, 2023

tecmusti commented Dec 31, 2023

wswebcreation commented Dec 31, 2023 • edited Loading

tecmusti commented Dec 31, 2023

wswebcreation commented Dec 31, 2023

ronenempathy commented Dec 31, 2023

wswebcreation commented Dec 31, 2023

ronenempathy commented Dec 31, 2023 • edited Loading

wswebcreation commented Dec 31, 2023

gregavola commented Dec 31, 2023

dafilmorais commented Dec 31, 2023 • edited Loading

wswebcreation commented Dec 31, 2023

wswebcreation commented Dec 31, 2023

sarunmrzn commented Dec 31, 2023

gregavola commented Dec 31, 2023

dafilmorais commented Dec 31, 2023

twercedev commented Dec 31, 2023

tecmusti commented Dec 31, 2023

ali-sao commented Dec 31, 2023

Harisene commented Jan 1, 2024

Harisene commented Jan 1, 2024

mina4gerges commented Jan 1, 2024

agrittiwari commented Jan 1, 2024

sdarwin commented Jan 1, 2025

userdocs commented Jan 1, 2025 • edited Loading

sdarwin commented Jan 1, 2025

userdocs commented Jan 1, 2025

Akifcan commented Jan 1, 2025

jpieper commented Jan 4, 2025

jtvargas commented Jan 6, 2025

genesiscz commented Jan 6, 2025

genesiscz commented Jan 6, 2025

jtvargas commented Jan 6, 2025

EnginKoyuncu commented Jan 7, 2025

Copyright (c) Meta Platforms, Inc. and affiliates.

This source code is licensed under the MIT license found in the

LICENSE file in the root directory of this source tree.

Pinning to the same version as React.podspec.

Copyright (c) Meta Platforms, Inc. and affiliates.

This source code is licensed under the MIT license found in the

LICENSE file in the root directory of this source tree.

Patched due to issue #843

Pinning to the same version as React.podspec.

Lazar4o commented Jan 7, 2025

sdarwin commented Jan 7, 2025 • edited Loading

meramsey commented Jan 15, 2025

edouard-claude commented Jan 20, 2025

misaelriojasftf commented Jan 22, 2025

Errors

Solution

wswebcreation commented Dec 31, 2023 •

edited

Loading

ronenempathy commented Dec 31, 2023 •

edited

Loading

dafilmorais commented Dec 31, 2023 •

edited

Loading

userdocs commented Jan 1, 2025 •

edited

Loading

sdarwin commented Jan 7, 2025 •

edited

Loading