Repository navigation
No exceptions or logs shown in flutter run on physical iOS 13 phone #41133
Description
Activity
- 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 - 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 - addedplatform-iosiOS applications specificallyiOS applications specifically
on Sep 23, 2019 So your app works, you just don't get debug output do I understand this right?
@escamoteur Correct.
- addedtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
on Sep 23, 2019 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.
@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.
- 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 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.
Reacted by Christopher Fujino, Jose Tapizquent, Luis and HeavnTeam@stx is this correct? It only happens on a physical device?
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.
Reacted by Tim Mividi, Luis and Cemal Y. Dalar@escamoteur Just tested this and can also confirm that logs work on the iOS 13 simulator.
Reacted by Christopher Fujino, Jarvis, Ryan Ramchandar and Cemal Y. Dalar67 remaining items
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 releaseWants happening with iPhone 11 ???
I have met the same question.
iPhone 11 pro max could't work.working with
v1.17.1NOT 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 issueWorking for me. iPhone 11 13.4.1. 🤷
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.
Reacted by Eric Platon, Bahri Rizaldi, Arpit Mathur, Dayyan Sisson and Jido ParkMine is not working
(Channel stable, v1.17.1, on Mac OS X 10.15.4 19E2269)
(Physical iOS 13 device, iPhone X)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 appearReacted by Liam, Tim Lehmann and Christian MürtzThe only way it shows up is if you run the Debug tool rather then going "flutter run" in Visual Studio Code
I'm using
1.17.5and also don't see any plugin outputs from Swift (usingprintorNSLog) 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.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
can we please fix this
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.
- locked as resolved and limited conversation to collaborators
on Aug 10, 2020 This should be fixed as of #66399.
Everything is at latest update. Device is an iPhone X on iOS 13.
The only thing that ever appears is the following:
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.