-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
The boost_1_76_0.tar.gz file is not in GZIP format #5542
Comments
Hey! 👋 The issue doesn't seem to contain a minimal reproduction. Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem? |
facing the same issue. any solution? |
same issue |
i have the same issue, any updates? |
Any Updates? |
same issue |
Same error, needs urgent attention |
anyone found a solution ? |
any solution yet? |
Currently, the ball is here : |
Any updates on the issue prepareBoost failed |
Still didn't fix it
I think it's a global issue
…On Mon, 1 Jan 2024, 8:21 am Linu Husain N K, ***@***.***> wrote:
Any updates on the issue prepareBoost failed
—
Reply to this email directly, view it on GitHub
<#5542 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXDYJW5PMAPXLXO7YZNGOHTYMJPX3AVCNFSM6AAAAABBIDFCWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZTGE4TSMBVGM>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Jfrog redirects the boost source download to this https://landing.jfrog.com/reactivate-server/boostorg with an account reactivation notice. Just replace
in
Then you can also |
I wasn't able to get it to work, has anyone tried this ? |
It worked for me. Make sure to run |
It's my android build that's failing, it's the same error message that's why I'm on this thread |
has anyone solved it yet?. the solutions provided aren't fixing it |
For Android, one quick workaround is to create patch-package for package react-native-reanimated. Just replace
in
This should fix the android build issue for timebeing. @Temitope-Emmanuel Make sure to delete the previously downloaded file boost_1_76_0.tar.gz in react-native-reanimated/android/build/downloads |
what about for managed workflow |
This worked for me. Make sure to delete the previously downloaded file |
@ravisharnagat Thank for your solution Its worked for me to generate Android build |
Does anyone able to solve this issue on building in GitHub Actions/ Workflow? |
Is it resolved or apply patch, which would be better ? |
same issue |
@ravisharnagat thank you it works for me... i'm still confused abut GZIP format in reanimated...... |
The problem is not in "node_modules/react-native-reanimated" but in the "node_modules/react-native". Boost is a portable C++ source libraries need to the compilation : |
Raised boostorg/boost#849 |
temporary it's work, thanks! |
How do I set it in expo? I think when running "eas build", all the dependencies are uploaded to the cloud server and download packages automatically so I can't change the code or values in the packages. How can I do it? |
it is solved Migrate boost download away from JFrog |
Is it fixed for expo-module-core too? |
As mentioned above, def srcUrl = "https://boostorg.jfrog.io/artifactory/main/release/${transformedVersion}/source/boost_${BOOST_VERSION}.tar.gz" def srcUrl = "https://sourceforge.net/projects/boost/files/boost/${transformedVersion}/boost_${BOOST_VERSION}.tar.gz" And then create a patch file using this command - Temporary workaround. Working for me |
Fixed the Issue with Boost Library Step 1: Update URL in ReactAndroid Build Script
Step 2: Update URL in Expo Modules Core
Step 3: Apply the Patches After making the changes, run the following commands to apply the patches:
|
I applied the patch to:
Now I get this error:
Not sure how hermes was effected. I have deleted node_modules and cleared the android build cache but to no avail. Anyone else seen this? |
same issue here trying to generate builds in AppCenter |
A solution given in another issue seems to work: #3590 (comment) But, how to make this change so that it works in a ci/cd as well? |
I applied the patch only to react-native and react-native-reanimated since i am not using expo and it worked in react-native you also need to patch an additional file other than the build.gradle (see facebook/react-native#42180) |
same |
I'm getting error for iOS too, during pod install commando in App Center. What I need to change before creating the patch?
|
@lucianomlima React Native posted a workaround to fix the ios error. facebook/react-native#42180 (comment) |
I tried this method. But still says the same message. Are there any steps I have to do after patch-package? |
## **Description** * RN was failing because of a down 3rd parties dependencies called [boost](https://www.boost.org/) which is a C++ utility library. * RN suggested [this fix](facebook/react-native#42180) * But another file in react-native [needed to be updated for Android](software-mansion/react-native-reanimated#5542) as well _The boost library URL needed to be updated in 2 places_ **This PR incorporates both updates of the boost library download URL into the patch of react-native** Smoke tests passing: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/675c4c9f-22b4-461b-803c-04d3db6dd595 <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> ## **Related issues** Fixes: ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've clearly explained what problem this PR is solving and how it is solved. - [ ] I've linked related issues - [ ] I've included manual testing steps - [ ] I've included screenshots/recordings if applicable - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. - [ ] I’ve properly set the pull request status: - [ ] In case it's not yet "ready for review", I've set it to "draft". - [ ] In case it's "ready for review", I've changed it from "draft" to "non-draft". ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
## **Description** * RN was failing because of a down 3rd parties dependencies called [boost](https://www.boost.org/) which is a C++ utility library. * RN suggested [this fix](facebook/react-native#42180) * But another file in react-native [needed to be updated for Android](software-mansion/react-native-reanimated#5542) as well _The boost library URL needed to be updated in 2 places_ **This PR incorporates both updates of the boost library download URL into the patch of react-native** Smoke tests passing: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/675c4c9f-22b4-461b-803c-04d3db6dd595 <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> ## **Related issues** Fixes: ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've clearly explained what problem this PR is solving and how it is solved. - [ ] I've linked related issues - [ ] I've included manual testing steps - [ ] I've included screenshots/recordings if applicable - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. - [ ] I’ve properly set the pull request status: - [ ] In case it's not yet "ready for review", I've set it to "draft". - [ ] In case it's "ready for review", I've changed it from "draft" to "non-draft". ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
## **Description** Cherry pick PR for: * RN was failing because of a down 3rd parties dependencies called [boost](https://www.boost.org/) which is a C++ utility library. * RN suggested [this fix](facebook/react-native#42180) * But another file in react-native [needed to be updated for Android](software-mansion/react-native-reanimated#5542) as well _The boost library URL needed to be updated in 2 places_ **This PR incorporates both updates of the boost library download URL into the patch of react-native** Smoke tests passing: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/675c4c9f-22b4-461b-803c-04d3db6dd595 <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> ## **Related issues** Fixes: ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've clearly explained what problem this PR is solving and how it is solved. - [ ] I've linked related issues - [ ] I've included manual testing steps - [ ] I've included screenshots/recordings if applicable - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. - [ ] I’ve properly set the pull request status: - [ ] In case it's not yet "ready for review", I've set it to "draft". - [ ] In case it's "ready for review", I've changed it from "draft" to "non-draft". ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. ## **Description** <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> ## **Related issues** Fixes: ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've clearly explained what problem this PR is solving and how it is solved. - [ ] I've linked related issues - [ ] I've included manual testing steps - [ ] I've included screenshots/recordings if applicable - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. - [ ] I’ve properly set the pull request status: - [ ] In case it's not yet "ready for review", I've set it to "draft". - [ ] In case it's "ready for review", I've changed it from "draft" to "non-draft". ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. --------- Co-authored-by: sethkfman <seth.kaufman@consensys.net>
This worked for me. Thanks for the temp fix! |
i have tried this fix but now i am having problem with /node_modules/react-native/ReactCommon/cxxreact/CxxModule.h:15:10: fatal error: 'folly/dynamic.h' file not found |
This worked for me. Thanks for the fix! |
Install this package,
This solved my problem. |
Seems that is working now again, I tried to do some builds in AppCenter in IOS and Android and works fine! |
In short, the problem happened because the necessary jFrog servers were not working. The solution is to simply update the URL for the dependency repository. You can find an example of how to do this here: link. Alternatively, you can also wait for a few minutes until the servers are back online. For more detailed information, check out this link: link. |
Description
Getting following error on android build creation:
Steps to reproduce
Execution is failing for the step where boost is prepared, because the downloaded tar.gz file (https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.gz) is not present in gzip format. Please check the screenshot attached.
Snack or a link to a repository
github.com/eternal_mercy_2/test-reanimated
Reanimated version
3.3.0
React Native version
0.69.1
Platforms
Android
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: