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.

Sign up for GitHub

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

Jump to bottom

[docs] Update Upgrade Expo SDK #28457

Merged
merged 2 commits into from May 7, 2024
Merged

[docs] Update Upgrade Expo SDK #28457

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4290218
[docs] Update Upgrade Expo SDK
amandeepmittal Apr 25, 2024
f455746
Update expo-go.mdx
amandeepmittal May 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pages/get-started/expo-go.mdx
View file
Open in desktop
Expand Up @@ -47,7 +47,7 @@ The manifest is similar to an **index.html** on the web. It is served from the r

### SDK versions

Expo Go supports multiple [**SDK versions**](/versions/latest/). A new Expo SDK version is released approximately three times each year. Each time a new version is added to Expo Go, an old version is dropped. You can see the supported SDK versions in the Expo Go app by navigating to the settings page.
Expo Go supports the latest [**SDK version**](/versions/latest/) only. Each time a new version is added to Expo Go, the previous version is dropped.

<Collapsible summary="What if I open a project with an unsupported SDK version?">

Expand Down
12 changes: 7 additions & 5 deletions docs/pages/workflow/upgrading-expo-sdk-walkthrough.mdx
View file
Open in desktop
Expand Up @@ -9,7 +9,9 @@ import { Tabs, Tab } from '~/ui/components/Tabs';

> **info** We recommend upgrading SDK versions incrementally, one at a time. Doing so will help you pinpoint breakages and issues that arise during the upgrade process.

Expo maintains approximately 6 months of backward compatibility. Once an SDK version has been deprecated, you can no longer use it in the Expo Go app. SDK deprecations **will not** affect the standalone apps you have in production or your [development builds](/develop/development-builds/introduction/), and backwards compatibility for older SDK versions on EAS services tends to be much longer, but not forever.
With a new SDK release, the latest version enters the current release status. This applies to Expo Go as it only supports the latest SDK version and previous versions are no longer supported. We recommend using [development builds](/develop/development-builds/introduction/) for production apps as the backwards compatibility for older SDK versions on EAS services tends to be much longer, but not forever.

If you are looking to install a specific version of Expo Go, visit [expo.dev/go](https://expo.dev/go). It supports downloads for Android devices/emulators and iOS simulators. However, due to iOS platform restrictions, only the latest version of Expo Go is available for installation on physical iOS devices.

## How to upgrade to the latest SDK version

Expand All @@ -27,8 +29,8 @@ Install the new version of the Expo package:
'# Install latest',
'$ npm install expo@latest',
'',
'# Install a specific SDK version (for example, SDK 49)',
'$ npm install expo@49',
'# Install a specific SDK version (for example, SDK 50)',
'$ npm install expo@50',
]}
/>

Expand All @@ -41,8 +43,8 @@ Install the new version of the Expo package:
'# Install latest',
'$ yarn add expo@latest',
'',
'# Install a specific SDK version (for example, SDK 49)',
'$ yarn add expo@49',
'# Install a specific SDK version (for example, SDK 50)',
'$ yarn add expo@50',
]}
/>

Expand Down