-
Notifications
You must be signed in to change notification settings - Fork 139
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
docs(rn): add callouts for expo tsconfig and deployment targets #1304
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd the label graphite-merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@moldy530 , Just a comment about setting the deployment target properly without editing the native files directly.
After running the above command for iOS, you need to update the `ios/Podfile.properties.json` to target iOS minimum version of 17.0 | ||
```json | ||
{ | ||
// ...other settings | ||
"ios.deploymentTarget": "17.0" | ||
} | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So with the Expo prebuild flow, we don't want to be touching the generated native files (i.e files in the ios
/ android
folders) cause they would get re-generated anytime the user does a Prebuild and our changes would be lost.
In this case we should tell the user to use expo-build-properties
to configure the deploymentTarget.
This updates the native properties on either platform using a Config Plugin which means anytime a Prebuild happens, Expo knows to read update the build config to whatever we set here.
The docs are here https://docs.expo.dev/versions/latest/sdk/build-properties/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh lemme try that
7e65197
to
b1bb334
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
a129185
to
97837b7
Compare
85c8544
to
5fc3a4e
Compare
5fc3a4e
to
8dd7a73
Compare
Pull Request Checklist
yarn test
)site
folder, and guidelines for updating/adding docs can be found in the contribution guide)feat!: breaking change
)yarn lint:check
) and fix any issues? (yarn lint:write
)PR-Codex overview
This PR primarily updates the documentation for the
React Native Signer
package, emphasizing the prerequisites, setup instructions, and compatibility with React Native's new architecture. It introduces a newprerequisites.mdx
file and integrates its content into various existing documentation files.Detailed summary
## Pre-requisites
inprerequisites.mdx
listing requirements for theReact Native Signer
.Alchemy Signer
being in Alpha from multiple files.Snippet
component to include prerequisite information inoverview.mdx
,setup-guide.mdx
,getting-started-rn-bare.mdx
, andgetting-started-expo.mdx
.getting started
sections across various files.