We found a temporary solution until the issue is resolved

move to

node_modules/react-native/third-party-podspecs/boost.podspec

spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2',
:sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

change to

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

Hi everyone. We are extremely sorry for the disruption. As I mention already, we don’t own the service where Boost is hosted, so this is not a part of our infra where we can intervene directly.

We are working on a solution to avoid this problem in the future, so bear with us for now. From your reports, I can see that the version affected are:

• 0.70
• 0.71
• 0.72
• 0.73

Please bear in mind that 0.70 is not supported anymore. We might consider to make a new release for the sake of this change, but that’s still up for discussion.

Please, stop adding comment like “+1” or “I’m affected too”, because this just adds noise to the issue and doesn’t make us work faster.

@prashantkamboj the issue is closed because the exact same incident happened around New Year’s Eve and then the infra recovered the 1st of January, so we closed the issue. Now, a week after, it is presenting again.

Workaround

To unblock yourself, you can apply the changes highlighted by this PR: https://github.com/facebook/react-native/pull/42118/files

For 0.72 and 0.73, these changes should be straight forward, as they are already in the monorepo setup, so the files path matches with the one of the PR.

For 0.70 and 0.71, we are not in the monorepo. To get the right path, remove the package/react-native from the two files paths. So, the paths are:

• For the build.gradle.kts: <your_project>/node_modules/react-native/ReactAndroid/build.gradle.kts
• For the boost.podspec: <your_project>/node_modules/react-native/third-party-podspecs/boost.podspec

It looks like it’s happening again to quite a few people. Could we please re-open this?

This is fixed now. Boost changed something that invalidated the checksum, but it is resolved now. Our CI is green: https://app.circleci.com/pipelines/github/facebook/react-native/39145/workflows/faa1c7e2-37d6-440b-8b93-abe665bd2087

This is fixed now. Boost changed something that invalidated the checksum, but it is resolved now. Our CI is green: https://app.circleci.com/pipelines/github/facebook/react-native/39145/workflows/faa1c7e2-37d6-440b-8b93-abe665bd2087

not fixed

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

The same case.

Happy New Year You All Guys!

same

Copyright © 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://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

This helped me --> ‘https://archives.boost.io/release/1.76.0/source/boost_1_76_0.tar.bz2’,

archives.boost.io as host for boost help me also

this issue has returned as of last night

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

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

Same here…

i have this issue now. @_@

• Facing the same issue… Running on React native 0.72.8, Boost 1.76.0

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

Copyright © 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://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

This helped me --> ‘https://archives.boost.io/release/1.76.0/source/boost_1_76_0.tar.bz2’,

Stuff like this reminds me why I move to Expo

for those with boost@1.76

spec.source = { :http => 'https://archives.boost.io/release/1.76.0/source/boost_1_76_0.tar.gz',
                  :sha256 => '7bd7ddceec1a1dfdcbdb3e609b60d01739c38390a5f956385a12f3122049f0ca' }

Quick way to find out: download the file and run sha256sum <filename>

Excellent! The temporary solution, as mentioned by others earlier, is effective. However, the issue is that we need to apply this solution every time we install fresh packages. Even creating a patch for these changes doesn’t work seamlessly. I’m still in search of a permanent fix.

for those with boost@1.76

spec.source = { :http => 'https://archives.boost.io/release/1.76.0/source/boost_1_76_0.tar.gz',
                  :sha256 => '7bd7ddceec1a1dfdcbdb3e609b60d01739c38390a5f956385a12f3122049f0ca' }

Quick way to find out: download the file and run sha256sum <filename>

+1 🤣

@abdelhamid-f-nasser I think this is a temporary solution. We should not do that after every yarn/npm install, it downloads from an archive I think it is safe

Still happening at RN 0.71.13.

here’s temporary solution using patch-package from (https://github.com/facebook/react-native/issues/42110#issuecomment-1872943368)

node_modules/react-native/third-party-podspecs/boost.podspec

spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.bz2',
:sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }
change to

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

I have found PRs which was made from RN developer and RN Team in Boost Repo.

https://github.com/boostorg/boost/issues/843 https://github.com/boostorg/boost/issues/845

Until they solve this prob, we might need to use this temporary solution…

We found a temporary solution until the issue is resolved

move to

node_modules/react-native/third-party-podspecs/boost.podspec

spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2',
:sha256 => '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' }

change to

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

resolved thanks