Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ios-deploy will not launch to ios13 device with "Device doesn't support wireless sync" #37699

Closed
christopherfujino opened this issue Aug 6, 2019 · 122 comments
Closed

ios-deploy will not launch to ios13 device with "Device doesn't support wireless sync" #37699

christopherfujino opened this issue Aug 6, 2019 · 122 comments
Assignees
@christopherfujino
Labels
c: regression It was better in the past than it is now e: device-specific Only manifests on certain devices tool Affects the "flutter" command-line tool. See also t: labels.
Milestone
September 2019

Comments

@christopherfujino
Copy link
Member

christopherfujino commented Aug 6, 2019 •
edited

Internal: b/141639365

UPDATE So this was actually two separate issues, this issue, which was fixed by updating the version of ios-deploy we distribute with the flutter tool to pick up an upstream fix (fixed here) and a change in iOS13 logging that resulted in the flutter tool not being able to connect to a Flutter application's observatory after it launched (meaning hot reload did not work). This was fixed later, here. Both fixes landed in v1.10.4, which is currently on the dev branch. There is still an oustanding issue with ios 13 that logs from physical devices are not readable, that is being tracked with #41133.

Split out from this issue by @kangwang1988

This is not directly related to macOS Catalina.

[!] Flutter (Channel alf_stable_v1.5.4, v1.5.4-hotfix.3-pre.28, on Mac OS X 10.15 19A471t, locale en)
    • Flutter version 1.5.4-hotfix.3-pre.28 at /Users/kylewong/Codes/Flutter/official/flutter
    • Framework revision acb8e3e9ea (23 hours ago), 2019-06-04 18:42:28 +0800
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)
    ✗ Downloaded executables cannot execute on host.
      See https://github.com/flutter/flutter/issues/6207 for more information

output of flutter run -v:

[        ] [ 49%] Copying /Users/kylewong/Codes/Flutter/intl/fx_intfish/build/ios/iphoneos/Runner.app/AppIcon76x76~ipad.png to device
[ +273 ms] [ 52%] CreatingStagingDirectory
[        ] [ 57%] ExtractingPackage
[        ] [ 60%] InspectingPackage
[  +27 ms] [ 60%] TakingInstallLock
[ +391 ms] [ 65%] PreflightingApplication
[  +39 ms] [ 65%] InstallingEmbeddedProfile
[   +8 ms] [ 70%] VerifyingApplication
[ +291 ms] [ 75%] CreatingContainer
[   +4 ms] [ 80%] InstallingApplication
[   +4 ms] [ 85%] PostflightingApplication
[   +2 ms] [ 90%] SandboxingApplication
[  +14 ms] [ 95%] GeneratingApplicationMap
[ +200 ms] [100%] Installed package build/ios/iphoneos/Runner.app
[ +556 ms] ------ Debug phase ------
[        ] Starting debug of 1c8e085cf2ff6fa27643ab4afec4bf4a077688af (D10AP, iPhone 7, iphoneos, arm64) a.k.a. 'KyleWong's iPhone'
connected through USB...
[ +220 ms] [  0%] Looking up developer disk image
[  +20 ms] [ 95%] Developer disk image mounted successfully
[  +83 ms] 2019-06-05 17:54:58.369 ios-deploy[50514:429547] [ !! ] Error 0xe800007f: Device doesn't support wireless sync.
AMDeviceStartService(device, CFSTR("com.apple.debugserver"), &gdbfd, NULL)
[   +2 ms] Failed to launch the application on device.
[   +1 ms] Installing and launching... (completed in 6.9s)
[        ] Could not install build/ios/iphoneos/Runner.app on 1c8e085cf2ff6fa27643ab4afec4bf4a077688af.
[        ] Try launching Xcode and selecting "Product > Run" to fix the problem:
[        ]   open ios/Runner.xcworkspace
[        ] Error launching application on KyleWong's iPhone.
@christopherfujino christopherfujino added the tool Affects the "flutter" command-line tool. See also t: labels. label Aug 6, 2019
@christopherfujino christopherfujino mentioned this issue Aug 6, 2019
Closed
@jmagman jmagman mentioned this issue Aug 29, 2019
Closed
@chwo
Copy link

chwo commented Sep 11, 2019

@christopherfujino I am getting the same error after upgrading to iOS 13 GM and Xcode 11 GM.

This issue seems to be a general issue of launching flutter apps on iOS 13 and does not only appear on devices connected through wifi as the title suggests. As you can see in the flutter run output from @kangwang1988 in the issue description and my output below this also happens for devices connected through USB.

Logs

[✓] Flutter (Channel stable, v1.9.1+hotfix.2, on Mac OS X 10.14.6 18G87, locale
    de-DE)
[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
[✓] VS Code (version 1.38.0)
[✓] Connected device (1 available)

[ +156 ms] [100%] Installed package build/ios/iphoneos/Runner.app
[ +154 ms] ------ Debug phase ------
[        ] Starting debug of 00008020-000E19963C09002E (D321AP, iPhone XS, iphoneos, arm64e) a.k.a. 'iPhone Xs' connected through USB...
[ +140 ms] [  0%] Looking up developer disk image
[  +17 ms] [ 95%] Developer disk image mounted successfully
[ +150 ms] 2019-09-11 10:23:56.513 ios-deploy[70666:22445778] [ !! ] Error 0xe800007f: Device doesn't support wireless sync. AMDeviceStartService(device,
CFSTR("com.apple.debugserver"), &gdbfd, NULL)
[   +5 ms] Could not install build/ios/iphoneos/Runner.app on 00008020-000E19963C09002E.
[        ] Try launching Xcode and selecting "Product > Run" to fix the problem:
[        ]   open ios/Runner.xcworkspace
[        ] Installing and launching... (completed in 9,6s)
[        ] Error launching application on iPhone Xs.
[   +3 ms] "flutter run" took 35.054ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:477:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:490:18)
#3      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#4      _rootRunUnary (dart:async/zone.dart:1132:38)
#5      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#6      _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#7      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#8      Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#9      Future._completeWithValue (dart:async/future_impl.dart:522:5)
#10     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#11     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#12     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#13     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#14     _rootRunUnary (dart:async/zone.dart:1132:38)
#15     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#20     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
#21     _rootRun (dart:async/zone.dart:1124:13)
#22     _CustomZone.run (dart:async/zone.dart:1021:19)
#23     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#24     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#25     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#26     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#27     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#28     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

@christopherfujino
Copy link
Member Author

cc @zanderso

@christopherfujino christopherfujino self-assigned this Sep 11, 2019
@christopherfujino christopherfujino added this to the September 2019 milestone Sep 11, 2019
@christopherfujino christopherfujino changed the title ios-deploy will not launch to wifi device ios-deploy will not launch to ios13 device Sep 11, 2019
@zanderso
Copy link
Member

It looks like there is an upstream issue for this: ios-control/ios-deploy#370. We'll have to try to repro and investigate if there are any workarounds.

@christopherfujino christopherfujino changed the title ios-deploy will not launch to ios13 device ios-deploy will not launch to ios13 device with "Device doesn't support wireless sync" Sep 11, 2019
@christopherfujino
Copy link
Member Author

@zanderso which I think is fixed with ios-deploy #385. If that works, we just have to roll that change into flutter; however, I'm worried that there may be another issue if it's also affecting chwo over usb.

@christopherfujino
Copy link
Member Author

UPDATE: I was able to get past this error by updating ios-deploy, however, now the tool is not connecting to the observatory, so I am continuing to investigate this.

@christopherfujino
Copy link
Member Author

it looks like idevicesyslog is not reading any logs from the device (it detects connect or disconnect signals, however)...

@christopherfujino
Copy link
Member Author

So I tried debugging flutter apps, running flutter apps, running non-flutter apps, changing system settings, and none of these produced any logs I could see in macOS's console app. The only logs I could get from the device where when I first attached it to my mac host: https://gist.github.com/christopherfujino/6e22a26d15c91fadd9feaf8fde97c5b4.

When comparing with an earlier version of ios, these syslogs are very busy.

@zanderso
Copy link
Member

/cc @cbracken @chinmaygarde in case there is an issue with the embedding's implementation of Dart's print().

@zanderso zanderso added e: device-specific Only manifests on certain devices engine flutter/engine repository. See also e: labels. c: regression It was better in the past than it is now labels Sep 12, 2019
@christopherfujino christopherfujino mentioned this issue Sep 12, 2019
Merged
@christopherfujino
Copy link
Member Author

christopherfujino commented Sep 13, 2019 •
edited

NOTE: I landed #40398 to solve the ios-deploy issue. However, on an iPhone Xr I'm seeing another issue, which is no (iPhone) device logs, so I will open a new issue for that.

@christopherfujino christopherfujino mentioned this issue Sep 13, 2019
Closed
@chwo
Copy link

chwo commented Sep 16, 2019

@christopherfujino I retried running flutter apps on iOS 13 with your iOS-deploy fix on the master channel.

As described in this issue #40542, the ios-deploy error message is gone but flutter run is stuck in the Installing and launching... phase. As a result only the launch screen appears on the device.

Flutter Doctor 
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.10.3-pre.45, on Mac OS X 10.14.6 18G87, locale
   de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
[✓] VS Code (version 1.38.1)
[✓] Connected device (1 available)

@sfarestam
Copy link

sfarestam commented Sep 16, 2019 •
edited

I confirm this. The master channel version will upload and run applications but doesn't support hot reloading and gets stuck in the Installing and launching... phase when executed from vscode.

@christopherfujino I retried running flutter apps on iOS 13 with your iOS-deploy fix on the master channel.
As described in this issue #40542, the ios-deploy error message is gone but flutter run is stuck in the Installing and launching... phase. As a result only the launch screen appears on the device.

@christopherfujino
Copy link
Member Author

christopherfujino commented Sep 16, 2019 •
edited

@chwo @sfarestam I'm glad you're seeing the same thing as me (if you wanna see more logs, you can do flutter run -v. I have a fix for this which I hope to land to master today. Please stay tuned (at #40448)!

@sfarestam
Copy link

sfarestam commented Sep 17, 2019 •
edited

I have found a workaround.

  1. execute flutter run from terminal window 1
Launching lib/main.dart on iphone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: XXXXXXXXXX
Running pod install...                                              1.2s
Running Xcode build...
 ├─Assembling Flutter resources...                           6.8s
 └─Compiling, linking and signing...                         6.2s
Xcode build done.                                           14.8s
Installing and launching...
(This is taking an unexpectedly long time.)       ⣟

then (after the application has deployed to the phone and loaded), open a second terminal window and run flutter attach:

% flutter attach
Checking for advertised Dart observatories...
Checking for available port on com.example.app
Checking for authentication code for com.example.app
Syncing files to device iphone...                               1,539ms

🔥  To hot reload changes while running, press "r". To hot restart (and rebuild state), press "R".
An Observatory debugger and profiler on iphone is available at: http://127.0.0.1:1024/SyZKqcxGFKI=/
For a more detailed help message, press "h". To detach, press "d"; to quit, press "q".

Performing hot reload...
Reloaded 1 of 474 libraries in 219ms.

It is now possible to perform hot reloading by typing r in the terminal window running flutter attach

@iusn
Copy link

iusn commented Sep 19, 2019

hello
I have the same error.
use USB conenct iphone ios 13
Flutter (Channel stable, v1.9.1+hotfix.2, on Mac OS X 10.14.5 18F132, locale en-CN) • Flutter version 1.9.1+hotfix.2 at /Users/nero/Documents/flutter • Framework revision 2d2a1ffec9 (12 days ago), 2019-09-06 18:39:49 -0700 • Engine revision b863200c37 • Dart version 2.5.0

when run code
flutter run
the error is
ios-deploy[25585:1167569] [ !! ] Error 0xe800007f: Device doesn't support wireless sync. AMDeviceStartService(device, CFSTR("com.apple.debugserver"), &gdbfd, NULL) Could not install build/ios/iphoneos/Runner.app on fdd2327d66c65fd8e3f5eac3f29f39628bf7138f. Try launching Xcode and selecting "Product > Run" to fix the problem: open ios/Runner.xcworkspace

when run same project in xcode there is no error.

thank you

@christopherfujino
Copy link
Member Author

christopherfujino commented Sep 19, 2019 •
edited

@iusn this was fixed by #40447 and is currently on dev.

@wederchr
Copy link

@christopherfujino Thanks for the update. Will that be merged into stable as a hotfix?

@escamoteur
Copy link
Contributor

How do you know they didn't change anything? I was told they changed things till late in the beta.

@endrelovas
Copy link

How do you know they didn't change anything? I was told they changed things till late in the beta.

Upon official release of iOS13 and uninstalling the beta provisioning profile did not update iOS just reported to be up to date. Unlike a year ago when it did as GM was different than release.

@nohli
Copy link
Contributor

nohli commented Sep 27, 2019

@escamoteur, it's Apple being Apple ... again, I don't see much point in making a beta and a gold master, if they still have a lot of bugs and fixes in them, they just dropped a 13.1, I think The problem is more Apple than the Flutter team, we are all in the same boat, so a definitive solution will come out, I was testing the changes to our iOS 12 application myself, because of these problems with iOS 13.

iOS13.1 beta has been out for many weeks. iOS13 beta for months. And we still have these problems. Hard to blame apple this time. GM was out for 4 or 5 weeks or so by now (and no, Apple change nothing between the two). Still we have no stable release for iOS13 support.

http://www.thinkybits.com/blog/iOS-versions/

The latest version of iOS 13.1 is out for nine days (if they didn't change anything from GM to release, as you said).

So about 1.29 weeks. I don't see how this would qualify as "4 to 5 weeks or so".

Some problems didn't even get fixed in iOS 13, like textfield crashes and - without any change in flutter - after updating to 13.1 beta, the crashes disappeared. iOS 13 was kind of a mess, many (non-flutter) apps didn't work, or even stopped working after the second beta of iOS 13.1.

As I understand, the issue of this thread is that you can't test apps on your phone with hot reload (and running with Xcode would work)?

@yoryer
Copy link

yoryer commented Sep 27, 2019

@jerryzhoujw XCode was able to detect the device all the time without trouble, only flutter had problems.
With those commands the problem gone.

@henryadamgordon
Copy link

Well, I just update my iPhone 7 to 13.1 and also ran a flutter upgrade and everything seem working fine.

  • Flutter 1.9.1+hotfix.3

@endrelovas
Copy link

@escamoteur, it's Apple being Apple ... again, I don't see much point in making a beta and a gold master, if they still have a lot of bugs and fixes in them, they just dropped a 13.1, I think The problem is more Apple than the Flutter team, we are all in the same boat, so a definitive solution will come out, I was testing the changes to our iOS 12 application myself, because of these problems with iOS 13.

iOS13.1 beta has been out for many weeks. iOS13 beta for months. And we still have these problems. Hard to blame apple this time. GM was out for 4 or 5 weeks or so by now (and no, Apple change nothing between the two). Still we have no stable release for iOS13 support.

http://www.thinkybits.com/blog/iOS-versions/

The latest version of iOS 13.1 is out for nine days (if they didn't change anything from GM to release, as you said).

So about 1.29 weeks. I don't see how this would qualify as "4 to 5 weeks or so".

Some problems didn't even get fixed in iOS 13, like textfield crashes and - without any change in flutter - after updating to 13.1 beta, the crashes disappeared. iOS 13 was kind of a mess, many (non-flutter) apps didn't work, or even stopped working after the second beta of iOS 13.1.

As I understand, the issue of this thread is that you can't test apps on your phone with hot reload (and running with Xcode would work)?

I am refering beta release dates. Cheers.

@nohli
Copy link
Contributor

nohli commented Sep 27, 2019

@escamoteur, it's Apple being Apple ... again, I don't see much point in making a beta and a gold master, if they still have a lot of bugs and fixes in them, they just dropped a 13.1, I think The problem is more Apple than the Flutter team, we are all in the same boat, so a definitive solution will come out, I was testing the changes to our iOS 12 application myself, because of these problems with iOS 13.

iOS13.1 beta has been out for many weeks. iOS13 beta for months. And we still have these problems. Hard to blame apple this time. GM was out for 4 or 5 weeks or so by now (and no, Apple change nothing between the two). Still we have no stable release for iOS13 support.

http://www.thinkybits.com/blog/iOS-versions/
The latest version of iOS 13.1 is out for nine days (if they didn't change anything from GM to release, as you said).
So about 1.29 weeks. I don't see how this would qualify as "4 to 5 weeks or so".
Some problems didn't even get fixed in iOS 13, like textfield crashes and - without any change in flutter - after updating to 13.1 beta, the crashes disappeared. iOS 13 was kind of a mess, many (non-flutter) apps didn't work, or even stopped working after the second beta of iOS 13.1.
As I understand, the issue of this thread is that you can't test apps on your phone with hot reload (and running with Xcode would work)?

I am refering beta release dates. Cheers.

Me too (as you can see in the link, which states that the last beta (before the release, which was four days ago and supposedly had no changes) was out for six days). Cheers

@endrelovas
Copy link

endrelovas commented Sep 28, 2019 via email

@escamoteur
Copy link
Contributor

@endrelovas iOS 13 changed a lot internally so they had to change the tooling.
The current beta works on ios13

@nohli
Copy link
Contributor

nohli commented Sep 28, 2019

#36267 (comment)

The major problems I had got fixed just through the first iOS 13.1 beta, without any changes in flutter...so how could you truly support something which is broken in itself.
(and as I said before, several big non-flutter apps didn't work on iOS 13)

Anyway, let's not discuss this further :-)

I hope, you can enjoy iOS 13.1 soon!

@REDIDSOFT
Copy link

Good evening gentlemen, one question, how long does it take for a patch like 1.9.1hf3 to get out of dev and get into stable? Thanks.

@REDIDSOFT REDIDSOFT mentioned this issue Sep 29, 2019
Closed
@MarcelEdward
Copy link

Under Xcode debugging works, but not under android studio. There I get the 'Device doesn't support wireless sync' error. And that is true, I got the phone attached with usb.

I do not really care if I edit the dart files in xcode or android studio, but I cannot see the dart files or the lib folder in Xcode. Those are only visible in android studio. Not sure how to run the android emulator from Xcode either.

So I think I will have to edit the files in android studio and debug them in Xcode without hot releading ?

@christopherfujino
Copy link
Member Author

@MarcelEdward your situation has been fixed on beta, and should be hotfixed into stable soon.

@zanderso
Copy link
Member

@JRAVILES We are currently monitoring crash rate and analytics for the hotfix on beta channel, and will promote the hotfix to stable when the numbers there look good. Thanks for your patience!

@cbracken cbracken removed the engine flutter/engine repository. See also e: labels. label Sep 30, 2019
@cbracken
Copy link
Member

@christopherfujino I've removed the engine label since I don't believe there's anything engine-related on this bug (in its current form). IIRC there's a followup engine issue which is to adopt os_log for logging, which is an engine issue. Would you mind cross-referencing that bug here for searchability?

@escamoteur
Copy link
Contributor

@cbracken do you mean this here #41133

@christopherfujino
Copy link
Member Author

@cbracken it's the one @escamoteur linked, #41133. I'll add this to the description.

@REDIDSOFT
Copy link

@JRAVILES We are currently monitoring crash rate and analytics for the hotfix on beta channel, and will promote the hotfix to stable when the numbers there look good. Thanks for your patience!
Thanks @zanderso, this is not a great framework, This is THE BEST! Cheers.

@tvolkert
Copy link
Contributor

tvolkert commented Oct 1, 2019

FYI, the build containing this fix (v1.9.1+hotfix.4) has been promoted to the stable channel.

There remain two known issues with physical iOS 13 devices & Flutter tooling:

@enricobenedos enricobenedos mentioned this issue Oct 4, 2019
Closed
@jmagman jmagman mentioned this issue Oct 4, 2019
Closed
@lifenautjoe
Copy link

lifenautjoe commented Oct 11, 2019 via email

@christopherfujino
Copy link
Member Author

@lifenautjoe that is this issue, which we are actively looking at. Please follow there for updates!

@mabu-dev
Copy link

Well, I just update my iPhone 7 to 13.1 and also ran a flutter upgrade and everything seem working fine.

  • Flutter 1.9.1+hotfix.3

This worked for me 100%!

@calebisstupid calebisstupid mentioned this issue Dec 3, 2019
Closed
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@christopherfujino christopherfujino

Labels
c: regression It was better in the past than it is now e: device-specific Only manifests on certain devices tool Affects the "flutter" command-line tool. See also t: labels.
Projects
None yet
Milestone
September 2019
Development

No branches or pull requests