builder
builder copied to clipboard
BuilderIO
Fix: React Native SDK
Description
Handle multiple compatibility issues with Expo 50+
- async storage: handle SSR/static rendering
- async storage: add
regenerator-runtimepolyfill - include source in build as per https://callstack.github.io/react-native-builder-bob/build#source
- update e2e and snippets to use Expo 50+
TODO:
- [x] fix react-native-render-html
defaultPropsusage - [x] fix development builds
- [ ] test development builds
- [ ] add detox e2e test
🦋 Changeset detected
Latest commit: 2ee5fea0c6e6c515e6e58f26e362d1bc8833f8bf
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 1 package
| Name | Type |
|---|---|
| @builder.io/sdk-react-native | Patch |
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
![changeset-bot[bot] avatar](https://avatars.githubusercontent.com/in/28616?v=4 "Published by a pub.dev verified publisher"){kind=small}
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| nextjs-app-router-example | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 25, 2024 7:42pm |
| nextjs-pages-router-example | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 25, 2024 7:42pm |
| remix-gen2-example | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 25, 2024 7:42pm |
| svelte-vite-example | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 25, 2024 7:42pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
☁️ Nx Cloud Report
CI is running/has finished running commands for commit 2ee5fea0c6e6c515e6e58f26e362d1bc8833f8bf. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this CI Pipeline Execution
| 🟥 Failed Commands |
|---|
nx test @e2e/angular-ssr |
✅ Successfully ran 34 targets
nx test @e2e/next-app-dirnx test @e2e/angularnx test @e2e/qwik-citynx test @e2e/vuenx test @e2e/nuxtnx test @e2e/sveltekitnx test @e2e/sveltenx test @e2e/react-nativenx test @e2e/next-pages-dirnx test @e2e/solidnx test @e2e/remixnx test @e2e/reactnx test @e2e/next-app-dir-clientnx test @e2e/solid-startnx test @e2e/hydrogennx test @snippet/solidnx test @e2e/gen1-reactnx test @e2e/gen1-remixnx test @snippet/react-nativenx test @snippet/angular-ssrnx test @snippet/vuenx test @snippet/sveltenx test @e2e/gen1-nextnx test @snippet/sveltekitnx test @snippet/next-app-dir-clientnx test @snippet/nuxtnx test @snippet/reactnx test @snippet/qwik-citynx test @snippet/next-app-dirnx test @snippet/next-pages-dirnx test @snippet/angularnx test @builder.io/sdksnx typecheck @builder.io/sdksnx build @builder.io/sdk
Sent with 💌 from NxCloud.
![nx-cloud[bot] avatar](https://avatars.githubusercontent.com/in/80458?v=4 "Published by a pub.dev verified publisher"){kind=small}
⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.
Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
🔎 Detected hardcoded secrets in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9071768 | Triggered | Generic High Entropy Secret | f49e5f449bbafb7a40f5fa3d880e7560b3638999 | packages/sdks-tests/src/specs/symbol-tracking.ts | View secret |
| 11707119 | Triggered | Generic High Entropy Secret | 80b2e717df538d72a16c4e3aafbfc0e4f21ea38b | packages/sdks/snippets/react-native/app/[...slug].tsx | View secret |
| 11707119 | Triggered | Generic High Entropy Secret | a055b688632f84759a3588b2a4794e0e4e032b3c | packages/sdks/snippets/react-native/App.tsx | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
![gitguardian[bot] avatar](https://avatars.githubusercontent.com/in/46505?v=4 "Published by a pub.dev verified publisher"){kind=small}