Skip to content

Error installing boost Verification checksum was incorrect #843

Open

Description

@wswebcreation

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

Activity

  1. RahulSingh225 commented on Dec 31, 2023

    @RahulSingh225

    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

  2. vinpro24 commented on Dec 31, 2023

    @vinpro24

    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

  3. codeion commented on Dec 31, 2023

    @codeion

    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

  4. tecmusti commented on Dec 31, 2023

    @tecmusti

    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

  5. wswebcreation commented on Dec 31, 2023

    @wswebcreation
    Author

    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 😅

  6. tecmusti commented on Dec 31, 2023

    @tecmusti

    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.

  7. wswebcreation commented on Dec 31, 2023

    @wswebcreation
    Author

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

    1. Install patch-package:

      npm install --save-dev patch-package postinstall-postinstall
    2. 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
    1. 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/.
    2. 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.
  8. ronenempathy commented on Dec 31, 2023

    @ronenempathy

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

  9. wswebcreation commented on Dec 31, 2023

    @wswebcreation
    Author

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

    Yes:

    1. Go to node_modules/react-native/third-party-podspecs from the root of your project
    2. check the boost.podspec for the version you need to use
    3. check https://sourceforge.net/projects/boost/files/boost/ for the link of the file you need to have
    4. get the checksum
    5. Follow the steps from Error installing boost Verification checksum was incorrect #843 (comment)
  10. ronenempathy commented on Dec 31, 2023

    @ronenempathy

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

  11. wswebcreation commented on Dec 31, 2023

    @wswebcreation
    Author

    @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

    image

  12. gregavola commented on Dec 31, 2023

    @gregavola

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

  13. dafilmorais commented on Dec 31, 2023

    @dafilmorais

    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
  14. wswebcreation commented on Dec 31, 2023

    @wswebcreation
    Author

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

    What do you mean?

  15. wswebcreation commented on Dec 31, 2023

    @wswebcreation
    Author

    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

  16. 114 remaining items

  17. AliHaidar110 commented on Mar 11, 2025

    @AliHaidar110

    yep try using a vpn solved it for me after that I had to turn it of for another package :)

  18. gauravsbagul commented on Apr 8, 2025

    @gauravsbagul

    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

    also after doing this change if you get checksum mismatch issue, replace 6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e this with expected checksum

  19. michtntbrighte commented on Apr 9, 2025

    @michtntbrighte

    How to fix it for now is:

    1. check what version your boost.podspec is using
    2. compare the SHA and link from the Boost official website

    In my case I'm using 1.76, the url I use is https://archives.boost.io/release/1.76.0/source/boost_1_76_0.tar.bz2

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

  20. MadelineCollier commented on Apr 18, 2025

    @MadelineCollier

    This issue is fixed in React Native 0.75, (see fix here: react/react-native@d274826). I have opened a cherry-pick request to hopefully back-merge the fix to older versions of React Native (0.71-0.74) here: reactwg/react-native-releases#902

    If this pick-request gets rejected (fairly likely as releases of RN <=0.76.x are now unsupported) then this fix should still work for older versions such as RN 0.71.

  21. tibic commented on Apr 19, 2025

    @tibic

    我遇到同样的问题,真令人抓狂

    Image
  22. sahilkashyap64 commented on Apr 19, 2025

    @sahilkashyap64

    if you are still getting the error

    Installing boost (1.76.0)
    
    [!] Error installing boost
    Verification checksum was incorrect, expected f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41, got 79e6d3f986444e5a80afbeccdaf2d1c1cf964baa8d766d20859d653a16c39848
    

    try this solution , adding a function on top of the podfile

    #996

  23. guruatdigni commented on May 21, 2025

    @guruatdigni

    don't go for pod install or cocopod update. i have spend 4 to 5 hours fixed by myself.

    https://www.boost.org

    use this website and select the version you have used currently pick the checksum (SHA256) and copy the link.

  24. wenyiweb commented on May 23, 2025

    @wenyiweb
    1. npm install --save-dev patch-package postinstall-postinstall

    2. package.json scripts add "postinstall": "patch-package"

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

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

    1. npx patch-package react-native

    2. cd ios && pod install

  25. GourabSanyal commented on May 23, 2025

    @GourabSanyal

    was fixed when I changed the react native version from 71.14.0 to 71.15.0.

    Did regular cleaning and reinstall, and everything worked fine.

    also you can check this out : react/react-native#42180

  26. rodrigotoledo commented on Jun 3, 2025

    @rodrigotoledo
    1. npm install --save-dev patch-package postinstall-postinstall
    2. package.json scripts add "postinstall": "patch-package"
    3. modify node_modules/react-native/third-party-podspecs/boost.podspec

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

    1. npx patch-package react-native
    2. cd ios && pod install

    This is a really good code to solve the problem.

  27. mustafazeb381-123 commented on Aug 10, 2025

    @mustafazeb381-123

    @wswebcreation thankyou so much sir you save my day

  28. Samama-Zargham commented on Sep 29, 2025

    @Samama-Zargham

    **- Go to node_modules/react-native/third-party-podspecs from the root of your project

    • check the boost.podspec file**

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

    only change this url https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2
    to this
    https://sourceforge.net/projects/boost/files/boost/1.83.0/boost_1_83_0.tar.bz2

    **and than make patch by installing
    patch-package postinstall-postinstall
    Run this Comand to create patch
    npx patch-package react-native

    and now BOOM😃 install pods by running
    cd ios pod install**

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions