首页 > 解决方案 > 无法在 Expo Go 应用中打开 react-native 应用

问题描述

在我发布我的 react-native 应用程序后,expo-cli publish我得到以下结果:

› Expo SDK: 38.0.0
› Release channel: default
› Workflow: Bare

- Optimization: Project may contain uncompressed images. Optimizing image assets can improve app size and performance.
  To fix this, run npx expo-optimize. Learn more: https://docs.expo.io/distribution/optimizing-updates/#optimize-images

Building optimized bundles and generating sourcemaps...
Starting Metro Bundler
Building iOS bundle
Building Android bundle
Finished building JavaScript bundle in 13254ms.
Building source maps
Finished building JavaScript bundle in 8302ms.
Finished building JavaScript bundle in 115ms.
Building asset maps
Finished building JavaScript bundle in 103ms.
Finished building JavaScript bundle in 385ms.
Finished building JavaScript bundle in 333ms.

Bundle                     Size
┌ index.ios.js          1.07 MB
├ index.android.js      1.08 MB
├ index.ios.js.map      4.07 MB
└ index.android.js.map   4.1 MB

 JavaScript bundle sizes affect startup time. Learn more: https://expo.fyi/javascript-bundle-sizes

Analyzing assets
Saving assets
No assets changed, skipped.

Uploading JavaScript bundles
Publish complete

当我继续我的 Expo Go 应用程序然后打开该应用程序时,我看到以下错误消息:

截屏

我找不到有同样问题的人。为什么我会收到此错误消息?

诊断:

Expo CLI 4.5.0 environment info:
    System:
      OS: macOS 11.3.1
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 12.14.1 - /usr/local/bin/node
      npm: 6.13.4 - /usr/local/bin/npm
    Managers:
      CocoaPods: 1.10.1 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    IDEs:
      Xcode: 12.4/12D4e - /usr/bin/xcodebuild
    npmPackages:
      react: 17.0.1 => 17.0.1 
      react-dom: ^17.0.2 => 17.0.2 
      react-native: 0.64.1 => 0.64.1 
      react-native-web: ^0.16.3 => 0.16.3 
      react-navigation: ^4.4.4 => 4.4.4 
    npmGlobalPackages:
      expo-cli: 4.5.0
    Expo Workflow: bare

标签: react-nativeexpo

解决方案


每当我遇到像你这样的情况时,我都会开始注释代码。从你的应用程序的根目录开始,注释掉它的一半并检查问题是否存在。如果仍然出现,请注释掉另一半并向下钻取代码树。


推荐阅读