Skip to content

Compatibility Matrix

This matrix explains the recommended support status for the expo-gaode-map package family across Expo SDK, React Native, platforms, and build workflows. It is not a promise that every historical combination has been tested one by one. It is a public maintenance baseline: what is verified, what is recommended, what is theoretical, what is legacy, and what is unsupported.

Status Legend

StatusMeaning
VerifiedTested by maintainers through examples, CI, or release flow
RecommendedCurrent mainline combination and first priority for fixes
TheoreticalVersion range and workflow should match, but not every combination is tested
LegacyKept for old projects, lower maintenance priority
Verify yourselfMay work, but is not covered by the default support baseline
UnsupportedThe workflow does not match, or it cannot run by design

Expo / React Native Compatibility

Expo SDKReact NativeRecommended package versioniOSAndroidNew ArchitectureEAS BuildStatus
SDK 56RN 0.85.xexpo-gaode-map@2.2.x / expo-gaode-map-navigation@2.0.xExample config verifiedExample config verifiedSupportedSupportedRecommended
SDK 55RN 0.83.xexpo-gaode-map@2.2.x / expo-gaode-map-navigation@2.0.xTheoreticalTheoreticalSupportedSupportedMaintained
SDK 54RN 0.81 / 0.82expo-gaode-map@2.2.x / expo-gaode-map-navigation@2.0.xTheoreticalTheoreticalSupportedSupportedMaintained
SDK 53 and lowerRN 0.79 / 0.80 and olderexpo-gaode-map@v1LegacyLegacyMostly legacy architectureVerify yourselfMaintained
SDK 52 and lowerOlder RN versionsexpo-gaode-map@v1 or olderVerify yourselfVerify yourselfNot recommendedVerify yourselfLegacy projects

Current mainline

The current example apps use Expo SDK 56 and React Native 0.85.x. New projects should prefer SDK 56 with expo-gaode-map@2.2.x or expo-gaode-map-navigation@2.0.x.

Package Compatibility

PackageExpo SDK 54+Expo SDK 53-New ArchitectureExpo GoDev BuildEAS Build
expo-gaode-mapRecommended 2.xUse v1SupportedUnsupportedSupportedSupported
expo-gaode-map-navigationRecommended 2.xVerify yourselfSupportedUnsupportedSupportedSupported
expo-gaode-map-web-apiSupportedSupportedNo native dependencySupportedSupportedSupported
expo-gaode-map-searchNo longer maintained as standalone2.2.33 legacy compatibilityNot recommendedUnsupportedVerify yourselfVerify yourself

Expo Go is not supported for native AMap SDKs

expo-gaode-map and expo-gaode-map-navigation depend on native AMap SDKs, so they do not run inside Expo Go. Use an Expo development build, EAS Build, or a local native build.

Verified Environments

DatePackage versionExpo SDKReact NativePlatformBuild workflowNew ArchitectureResult
2026-06-30expo-gaode-map@2.2.38SDK 56RN 0.85.xAndroid / iOS configexpo-doctor + dependency validation + example appSupportedPassed
2026-06-30expo-gaode-map-navigation@2.0.18SDK 56RN 0.85.xAndroid / iOS configDependency validation + navigation example smoke testsSupportedPassed
2026-06-30expo-gaode-map-web-api@2.0.xSDK 56RN 0.85.xJS / native runtimeDependency validation + example appsNo native dependencyPassed

Release Checklist

Before each release, maintainers should at least run the following checks. This does not mean every API is manually tested every time, but the core path should stay buildable, runnable, and diagnosable.

md
- [ ] yarn lint
- [ ] yarn test
- [ ] yarn build:core
- [ ] yarn build:navigation
- [ ] yarn build:web-api
- [ ] yarn test:example-navigation
- [ ] Android example local build or EAS Build verified
- [ ] iOS example local build or EAS Build verified
- [ ] MapView renders
- [ ] Location permission flow works
- [ ] Marker / Polyline / Polygon smoke test
- [ ] Native search smoke test
- [ ] Navigation example smoke test when releasing navigation
- [ ] Website docs build passes

Version Guidance

  • New Expo projects: use the latest Expo SDK and expo-gaode-map@2.x.
  • Navigation projects: use expo-gaode-map-navigation directly and do not install the core package together.
  • Expo SDK 53 and lower: pin expo-gaode-map@v1 and plan an upgrade path.
  • Standalone expo-gaode-map-search: only for legacy projects pinned to 2.2.33; new projects should use the built-in search APIs from core / navigation.