Skip to content

No exceptions or logs shown in flutter run on physical iOS 13 phone #41133

Description

@stx

Everything is at latest update. Device is an iPhone X on iOS 13.

The only thing that ever appears is the following:

Launching lib/main.dart on Virgo in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: [...]
Xcode build done.                                           31.6s
Checking for advertised Dart observatories...
Checking for available port on [...]
Checking for authentication code for [...]

Tried flutter clean + rm -rf Podfile.lock Pods/, rebooting, etc.

Can't move to non-master Flutter channels to test due to active iOS 13/Xcode 11 build bugs.

[✓] Flutter (Channel master, v1.10.6-pre.33, on Mac OS X 10.14.6 18G95, locale en-US)
    • Flutter version 1.10.6-pre.33 at /Users/james/Development/flutter
    • Framework revision 961f1b746d (2 hours ago), 2019-09-23 10:09:38 -0700
    • Engine revision b875c7a5ff
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 7c1821c4aa)

 
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/james/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.0, Build version 11A420a
    • CocoaPods version 1.7.4

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 38.2.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.38.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.4.1

[✓] Connected device (1 available)
    • Virgo • b01937a10ffe8461ea409b3bd137ac0bf8ecc921 • ios • iOS 13.0

• No issues found!

Activity

  1. changed the title [-]No exceptions or logs shown in flutter run (MacOS Mojave)[/-] [+]No exceptions or logs shown in flutter run[/+] on Sep 23, 2019
  2. changed the title [-]No exceptions or logs shown in flutter run[/-] [+]No exceptions or logs shown in flutter run after upgrade[/+] on Sep 23, 2019
  3. escamoteur commented on Sep 23, 2019

    @escamoteur
    Contributor

    So your app works, you just don't get debug output do I understand this right?

  4. stx commented on Sep 23, 2019

    @stx
    Author

    @escamoteur Correct.

  5. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Sep 23, 2019
  6. christopherfujino commented on Sep 23, 2019

    @christopherfujino
    Contributor

    Thanks for filing this @stx. This is related to #40448. This isn't a regression in Flutter, but rather that something changed in iOS 13 that we are no longer able to read logs. I worked around this in that issue by using mDNS to discover the app observatory, but we still need to fix the lack of logs.

  7. stx commented on Sep 23, 2019

    @stx
    Author

    @christopherfujino Thanks for looking into it. The app observatory logs are nearly unusable for us because they spam frames and we're animating constantly. Effectively, this means that we don't get to do iOS debugging until this is fixed.

  8. changed the title [-]No exceptions or logs shown in flutter run after upgrade[/-] [+]No exceptions or logs shown in flutter run on iOS 13[/+] on Sep 24, 2019
  9. IRIG commented on Sep 25, 2019

    @IRIG

    The title of this issue does not explicitly state that the problem occurs only with physical devices. In my case it happens only with physical iOS devices with iOS 13 but not with a iOS simulator with iOS 13.

  10. escamoteur commented on Sep 25, 2019

    @escamoteur
    Contributor

    @stx is this correct? It only happens on a physical device?

  11. divan commented on Sep 25, 2019

    @divan

    After switching my devices to iOS 13, also hit this issue, and can confirm that logs still work with simulator (XCode beta, simulator devices running iOS 13, string from simulator About page: Version 11.0 (SimulatorApp-912.1 SimulatorKit-570.3 CoreSimulator-681.5.1))

    Also, just in case, if I run app from XCode, logs are shown.

    My `flutter doctor` output
    $ flutter doctor
    Doctor summary (to see all details, run flutter doctor -v):
    [✓] Flutter (Channel master, v1.10.6-pre.29, on Mac OS X 10.14.6 18G95, locale en-ES)
    

    [✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    [✓] Xcode - develop for iOS and macOS (Xcode 11.0)
    [!] Android Studio
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    [!] Android Studio (version 3.3)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    [✓] VS Code (version 1.38.1)
    [✓] Connected device (2 available)

    ! Doctor found issues in 2 categories.

  12. stx commented on Sep 25, 2019

    @stx
    Author

    @escamoteur Just tested this and can also confirm that logs work on the iOS 13 simulator.

  13. 67 remaining items

  14. 0xdevvv commented on May 6, 2020

    @0xdevvv

    @joaowd this has been fixed on version 1.10.15. You can get the fix by switching to the dev channel. This will be in the next stable release of flutter.

    @joaowd is it solved? it happens again in 1.12.13+hotfix9...

    Yes!

  15. kafkalxh commented on May 7, 2020

    @kafkalxh

    Same problem here (more info);

    I have 2 iPhones (iPhone 7 and 11)
    iPhone 7 (13.3) this device works with the debug window
    iPhone 11 (13.3) this device does not work with the debug window
    Flutter: 1.12.13+hotfix.5. this is sable release

    Wants happening with iPhone 11 ???

    I have met the same question.
    iPhone 11 pro max could't work.

  16. lookfirst commented on May 14, 2020

    @lookfirst

    working with v1.17.1

  17. cihadturhan commented on May 17, 2020

    @cihadturhan

    NOT working with v1.17.1
    iPhone XR 13.4.1
    And, execution doesn't stop at breakpoints on first run. It works after I do a refresh.


    Edit: Apologies for the false alarm. It turns out flutter somehow couldn't compile my latest code (the code with prints) and that's why I didn't see the logs. This was completely different issue

  18. lookfirst commented on May 17, 2020

    @lookfirst

    Working for me. iPhone 11 13.4.1. 🤷

  19. thenexus00 commented on May 18, 2020

    @thenexus00

    I recently upgrade to the latest on the production branch and it is not working for me either now.

    logger.log() does nothing as well.

  20. ZhuBoao commented on May 25, 2020

    @ZhuBoao

    Mine is not working
    (Channel stable, v1.17.1, on Mac OS X 10.15.4 19E2269)
    (Physical iOS 13 device, iPhone X)

  21. brizaldi commented on May 26, 2020

    @brizaldi

    using latest master branch and still not working

    [✓] Flutter (Channel master, 1.19.0-2.0.pre.143, on Mac OS X 10.15.4 19E287, locale en-US)
    [✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    [✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    [✓] Android Studio (version 3.6)

    tested on iPhone 6S iOS version 13.3.1

    edit: i can use print() and somehow its the only thing that appeared inside my debug log, but the other debug message & exceptions did not appear

  22. thenexus00 commented on Jun 5, 2020

    @thenexus00

    The only way it shows up is if you run the Debug tool rather then going "flutter run" in Visual Studio Code

  23. ivnsch commented on Jul 4, 2020

    @ivnsch

    I'm using 1.17.5 and also don't see any plugin outputs from Swift (using print or NSLog) when starting the app from Flutter. Neither in the debug console in VSCode, in the console app or in Xcode. I see them if I run the iOS example app in Xcode. I'm using the simulator.

  24. papmodern commented on Jul 28, 2020

    @papmodern
    Contributor

    This is one of the biggest flaws of dart/flutter. Always I have to use dart devtools to see the console outputs. Also I'm heavily using generators and I have to use terminal to see the build-runner exceptions!!!

    P.S I'm a windows user

  25. owenkealey commented on Aug 9, 2020

    @owenkealey

    can we please fix this

  26. jmagman commented on Aug 10, 2020

    @jmagman
    Member

    This is a closed issue. If you are seeing a problem, please file a new GitHub issue and completely fill out the template so we know what version you're on and can investigate or duplicate to an open issue. Sometimes we investigate this complaint and the app isn't even running when people think it is due to a crash on launch.

    There are already several open issues tracking various manifestations of this like #44717 and #44718.

  27. locked as resolved and limited conversation to collaborators on Aug 10, 2020
  28. jmagman commented on Sep 23, 2020

    @jmagman
    Member

    This should be fixed as of #66399.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

a: debuggingDebugging, breakpoints, expression evaluationplatform-iosiOS applications specificallytoolAffects the "flutter" command-line tool. See also t: labels.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions