Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pod install error verification checksum was incorrect at boost (1.83.0) #42109

Closed
truongngodang opened this issue Dec 31, 2023 · 68 comments
Closed
Labels
Needs: Author Feedback Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Needs: Triage 🔍

Comments

@truongngodang
Copy link

Description

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

Steps to reproduce

  1. cd ios & pod install

React Native Version

0.73.1

Affected Platforms

Build - MacOS

Output of npx react-native info

System:
  OS: macOS 14.2.1
  CPU: (8) arm64 Apple M1 Pro
  Memory: 73.77 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 21.5.0
    path: /opt/homebrew/bin/node
  Yarn:
    version: 1.22.21
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.2.4
    path: /opt/homebrew/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.14.3
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11076708
  Xcode:
    version: 15.1/15C65
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /opt/homebrew/opt/openjdk@17/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.1
    wanted: 0.73.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Stacktrace or Logs

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

Reproducer

none

Screenshots and Videos

No response

@github-actions github-actions bot added Needs: Author Feedback Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. labels Dec 31, 2023
Copy link

⚠️ Missing Reproducible Example
ℹ️ We could not detect a reproducible example in your issue report. Please provide either:
  • If your bug is UI related: a Snack
  • If your bug is build/update related: use our Reproducer Template. A reproducer needs to be in a GitHub repository under your username.

@dantonio1401
Copy link

Having the same issue

@deeeed
Copy link

deeeed commented Dec 31, 2023

+1

@InquestApp-Admin
Copy link

same issue. started tonight

@deeeed
Copy link

deeeed commented Dec 31, 2023

The issue seems to be on jfrog.io, the download links are dead https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.gz

It seems to be the only mirror according to:
https://www.boost.org/users/history/version_1_76_0.html

@Artem-Kalugin
Copy link

The issue seems to be on jfrog.io, the download links are dead https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.gz

It seems to be the only mirror according to: https://www.boost.org/users/history/version_1_76_0.html

And even there links dont work, rederecting to dead site

@kdn0325
Copy link

kdn0325 commented Dec 31, 2023

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' }

@kimyoungjae96
Copy link

I solved it with this.

@netanelz-amdocs
Copy link

netanelz-amdocs commented Dec 31, 2023

@cortinico do you plan to fix it so we would not need to patch it? Any ETA?

I solved it with this.

@Jonathanide1
Copy link

Same issue.

@Yeasirarafat53
Copy link

same issue

1 similar comment
@ronCohen2
Copy link

same issue

@barghi
Copy link

barghi commented Jan 1, 2024

same here

@tyler-canton
Copy link

Same

@PerrettJ4
Copy link

same

3 similar comments
@harry-anderson
Copy link

same

@batkap
Copy link

batkap commented Jan 1, 2024

same

@GOlmedoFormosa
Copy link

same

kueda added a commit to inaturalist/SeekReactNative that referenced this issue Jan 2, 2024
* Fixes Croatian pluralization, which seemed to be legitimately broken
* Workaround for facebook/react-native#42109
* Ensure `npm test` runs with UTC time zone
@ngocle2497
Copy link

ngocle2497 commented Jan 2, 2024

same here, and RN 0.72.5 same

@abdymm
Copy link

abdymm commented Jan 2, 2024

same

1 similar comment
@ashherr
Copy link

ashherr commented Jan 2, 2024

same

@Daha62
Copy link

Daha62 commented Jan 2, 2024

boostorg/boost#843 - helped me, just change url from boostorg to sourceforge (checksum is the same)

@mittalkamal29
Copy link

Same issue

@SupriyaGo
Copy link

Not working

@hamdij0maa
Copy link

+1 🤣

@codebycarlos
Copy link

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

@codebycarlos
Copy link

For anyone struggling, this is what worked for me in the meantime. You can grab a copy elsewhere (e.g. SourceForge) and replace it with the one in your /node_modules.

This may come with security implications and you'll have to do it each time you run an npm install.

@rieger-jared
Copy link

Having the same issue

@rangga-synergy
Copy link

i have this issue now. @_@

@kidpollo
Copy link

kidpollo commented Jan 8, 2024

same

@rfahernandez
Copy link

Same here...

@garrett-vorce-mohara
Copy link

Experiencing this issue on React Native & App Center CI/CD

@c-zhenhao
Copy link

c-zhenhao commented Jan 8, 2024

same

the temp fix mentioned above works though: #42109 (comment)

@ngocpd-1250
Copy link

same here....

@thtRajasthaniGuy
Copy link

same here..... using react-native version 0.70.6

@doanhtrinh95
Copy link

same here....., Please help...!

@r-guerin0
Copy link

Also having the issue (running react-native@0.72.4)

@ts-ign0re
Copy link

The same case.

Happy New Year You All Guys!

@prateekuttreja2020
Copy link

prateekuttreja2020 commented Jan 8, 2024

  • 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

@LouisJS
Copy link

LouisJS commented Jan 8, 2024

Same issue as @prateekuttreja2020 . Running on React Native 0.70. Boost 1.76.0

@dimitris4
Copy link

dimitris4 commented Jan 8, 2024

same issue, react native v. 0.72.6 - only happens in the CI/CD pipeline though..

@prashantkamboj
Copy link

Same issue with me but why this issue is closed ?

@lluis-sancho
Copy link

Same error here. (0.71.6)

@cipolleschi
Copy link
Contributor

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

@binarybaba
Copy link

binarybaba commented Jan 8, 2024

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>

@sindhusingh
Copy link

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.

@D-Cabs
Copy link

D-Cabs commented Jan 8, 2024

Hi!
React V. 0.70.5 question. Im a bit unsure what to do as remove "package/react-native" from the path.

.../node_modules/react-native/ReactAndroid/build.gradle has

    src("https://archives.boost.io/release/${BOOST_VERSION.replace("_", ".")}/source/boost_${BOOST_VERSION}.tar.gz")
    onlyIfNewer(true)
    overwrite(false)
    dest(new File(downloadsDir, "boost_${BOOST_VERSION}.tar.gz"))

And .../node_modules/react-native/third-party-podspecs

  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://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.bz2',
                  :sha256 => 'f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41'}

I am unsure what to change like @cipolleschi mentioned.

Could somebody point me on what to change as issue is critical for me at the moment.

@matteodanelli
Copy link

Hi! React V. 0.70.5 question. Im a bit unsure what to do as remove "package/react-native" from the path.

.../node_modules/react-native/ReactAndroid/build.gradle has

task downloadBoost(dependsOn: createNativeDepsDirectories, type: Download) { src("https://archives.boost.io/release/${BOOST_VERSION.replace("_", ".")}/source/boost_${BOOST_VERSION}.tar.gz") onlyIfNewer(true) overwrite(false) dest(new File(downloadsDir, "boost_${BOOST_VERSION}.tar.gz")) }

And .../node_modules/react-native/third-party-podspecs

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://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.bz2', :sha256 => 'f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41' }

I am unsure what to change like @cipolleschi mentioned.

Could somebody point me on what to change as issue is critical for me at the moment.

You could check this. Maybe it helps

@abdymm
Copy link

abdymm commented Jan 8, 2024

Could somebody point me on what to change as issue is critical for me at the moment.

i guess you need to do the patch package by changing the source url

@cipolleschi
Copy link
Contributor

We have an official workaround and a pinned issue: #42180.
I'm locking this conversation.

@facebook facebook locked and limited conversation to collaborators Jan 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Needs: Author Feedback Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Needs: Triage 🔍
Projects
None yet
Development

No branches or pull requests