upgrading-expo

Upgrades Expo SDK versions in React Native apps with step-by-step guidance and validation.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/emilyLi2020/WAVE --skill upgrading-expo-emilyli2020
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrading-expo
Source: https://github.com/emilyLi2020/WAVE/tree/main/.agents/skills/upgrading-expo
Command: npx skills add https://github.com/emilyLi2020/WAVE --skill upgrading-expo-emilyli2020

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Upgrading Expo SDK versions often introduces breaking API changes, deprecated packages, and native configuration adjustments that can break existing React Native applications if not handled systematically, leading to hours of manual debugging and trial and error.

Core Features & Use Cases

  • End-to-End Upgrade Guidance: Step-by-step workflows for upgrading Expo SDK versions, including dependency updates, cache clearing, and prebuild steps for both Continuous Native Generation and bare workflow projects.
  • Version-Specific Migration References: Detailed guides for common breaking changes across SDK versions, including React 19 adoption, expo-av to expo-audio/video migrations, native tabs component updates, and react-navigation to expo-router transitions.
  • Post-Upgrade Housekeeping: Instructions for removing deprecated packages, updating configuration files, enabling new features like React Compiler and Hermes v1, and cleaning up obsolete project settings.
  • Use Case: A developer upgrading a production React Native app from Expo SDK 54 to 55 can use this skill to migrate all audio playback code from expo-av to expo-audio, update native tab imports to the new SDK 55 structure, and enable Hermes v1 for improved runtime performance without missing critical steps.

Quick Start

Use the upgrading-expo skill to upgrade your Expo project to the latest SDK version, migrate deprecated packages and APIs, and resolve any dependency or native configuration issues that arise during the upgrade process.

Frequently Asked Questions about upgrading-expo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade my Expo SDK version without breaking my React Native app?

To upgrade your Expo SDK version safely, follow a step-by-step workflow that covers dependency updates, cache clearing, and prebuild steps. This systematic approach manages breaking API changes and native configuration adjustments to ensure app stability.

How do I migrate deprecated Expo packages like expo-av during an SDK upgrade?

Migrating deprecated packages like expo-av during an SDK upgrade requires replacing them with newer alternatives such as expo-audio and expo-video. Detailed migration references provide specific steps for updating imports and APIs to match version-specific breaking changes.

What breaking changes should I expect when upgrading to the latest Expo SDK?

Breaking changes during an Expo SDK upgrade include React 19 adoption, native tabs component updates, and transitions from react-navigation to expo-router. Version-specific migration references detail these deprecated APIs and required native configuration adjustments.

Does this Expo SDK upgrade workflow support both bare workflow and Continuous Native Generation projects?

Yes, the Expo SDK upgrade workflow applies to both bare workflow and Continuous Native Generation projects. It provides tailored guidance for dependency updates, prebuild steps, and native configuration updates required for each specific project type.

What post-upgrade housekeeping is required after bumping my Expo SDK version?

Post-upgrade housekeeping after an Expo SDK version bump involves removing deprecated packages, updating configuration files, and cleaning up obsolete project settings. It also includes enabling new features like React Compiler and Hermes v1 for improved runtime performance.

Why does my React Native app crash after an Expo SDK version bump?

An app crash after an Expo SDK version bump typically results from unresolved breaking API changes, deprecated packages, or native configuration conflicts. Applying systematic dependency migration and following validation steps ensures post-upgrade app stability.