Upgrading expo-application from 57.x to 58.x
Comparison of the public API of expo-application 57.0.3 and 58.1.1, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 0 |
| Changed signatures | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 2 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
expo-application · PushNotificationServiceEnvironment | "development" | "production" | null | "production" | "development" | null |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
New exports (2)
| import | export | kind |
|---|---|---|
expo-application | AppleAppStoreEnvironment | type |
expo-application | getAppleStoreEnvironmentAsync | function |
Changelog between these versions
Text published by the package authors, shown as-is.
58.1.1
### Patch Changes
- [Internal] Bump precompiled artifacts due to ABI breakage in expo-modules-jsi, which makes `JavaScriptValue` a non-copyable struct. ([#51368](https://github.com/expo/expo/pull/51368) by [@tsapeta](https://github.com/tsapeta))
- [iOS] Remove the module class declarations from `expo-module.config.json`. Autolinking now detects the `@ExpoModule`-annotated classes. ([#49784](https://github.com/expo/expo/pull/49784) by [@tsapeta](https://github.com/tsapeta))58.1.0
### Minor Changes
- [iOS] Add `getAppleStoreEnvironmentAsync()`, which returns StoreKit's App Store environment for the running build (`'production'`, `'sandbox'` or `'xcode'`), so apps can tell TestFlight, App Review and development builds apart from App Store releases. ([#51209](https://github.com/expo/expo/pull/51209) by [@huntie](https://github.com/huntie))58.0.4
### Patch Changes
- [Android] Migrate to the Expo Modules API 2.0. ([#51077](https://github.com/expo/expo/pull/51077) by [@lukmccall](https://github.com/lukmccall))58.0.3
### Patch Changes
- Bump precompiled artifacts due to ABI breakage in expo-modules-jsi@58.0.6. ([#50881](https://github.com/expo/expo/pull/50881) by [@kitten](https://github.com/kitten))58.0.2
### Patch Changes
- Force-bump all packages, due to migration to changesets. ([#50762](https://github.com/expo/expo/pull/50762) by [@kitten](https://github.com/kitten))58.0.1
### 💡 Others
- [iOS] Rename the `EXApplication` pod to `ExpoApplication`. ([#50059](https://github.com/expo/expo/pull/50059) by [@tsapeta](https://github.com/tsapeta))
- [iOS] Migrate to the Expo Modules API 2.0 macros. ([#50059](https://github.com/expo/expo/pull/50059) by [@tsapeta](https://github.com/tsapeta))58.0.0
_This version does not introduce any user-facing changes._Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What are the breaking changes when upgrading expo-application from 57 to 58?
Between expo-application 57.0.3 and 58.1.1, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in expo-application 58?
0 exports or members are newly marked as deprecated in expo-application 58.1.1.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/expo-application/upgrade?from=57.0.3&to=58.1.1