Flutter 应用程序卡在 spalsh 屏幕 ios 上,但应用程序可在 Android 设备上运行

时间:2021-04-10 14:39:31

标签: ios flutter dart

我遇到了一个非常烦人的错误,我的应用程序在 Android 设备上运行良好,但在 ios 中它卡在启动屏幕上。我不知道如何解决这个问题,以任何可能的方式导致问题? //// 我正在 VMware MacOs Catalina 模拟器中测试我的 ios 应用

你认为 bug 来自代码还是来自系统?或者我如何确定导致问题的原因,任何可能的方法?

u flutter doctor -v
[✓] Flutter (Channel stable, 2.0.4, on Mac OS X 10.15.3 19D76 darwin-x64, locale
    ru-KZ)
    • Flutter version 2.0.4 at /Users/shukur/Downloads/flutter
    • Framework revision b1395592de (9 days ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from:
      https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK
      components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup
      for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.


[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C505
    ! Xcode 11.3.1 out of date (12.0.1 is recommended).
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.10.1

[✗] Chrome - develop for the web (Cannot find Chrome executable at
    /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[!] Android Studio (not installed)
    • Android Studio not found; download from
      https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup
      for detailed instructions).

[✓] Connected device (1 available)
    • iPhone 11 Pro Max (mobile) • 051A9E22-C99F-4531-B1AA-917BA8F0E332 • ios •
      com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator)

1 个答案:

答案 0 :(得分:0)

我只是通过在真正的 iPhone 设备上测试应用程序修复了这个错误! 干杯!