Skip to content

I'm not sure where this should go, but we should have the developer run npx expo-env-info and paste the contents in the bug report. Here's an example: #11

@jhampton

Description

@jhampton

We should have the developer run npx expo-env-info and paste the contents in the bug report. Here's an example:

  expo-env-info 2.0.7 environment info:
    System:
      OS: macOS 15.6
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 20.19.0 - ~/.nvm/versions/node/v20.19.0/bin/node
      Yarn: 1.22.19 - /usr/local/bin/yarn
      npm: 10.8.2 - ~/.nvm/versions/node/v20.19.0/bin/npm
    Managers:
      CocoaPods: 1.15.2 - /Users/andrew/.gem/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 24.5, iOS 18.5, macOS 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5
    IDEs:
      Android Studio: 2025.1 AI-251.27812.49.2514.14217341
      Xcode: 16.4/16F6 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^54.0.10 => 54.0.11 
      react-native: 0.81.4 => 0.81.4 
    npmGlobalPackages:
      eas-cli: 16.18.0
    Expo Workflow: bare

Originally posted by @sidorchukandrew in #10 (comment)

Metadata

Metadata

Labels

documentationImprovements or additions to documentationenhancementNew feature or request
No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions