How to fix HttpException: Connection closed before full header was received

Question

I have recently upgraded my flutter version in my app. But when I want to debug the application, it shows me the following error.

Error connecting to the service protocol: HttpException: Connection closed before full header was received, URI = http://127.0.0.1:50795/ws

Is there anyone facing the same issue after upgrading the flutter version? If is there any workaround, please share.

i ran "flutter clean" in terminal of VS code without turning off the WIFI first unfortunately. Now I have got so many errors like runApp isn't defined, all the build, .dart tool, .packages, has been deleted, . what should I do now? — Suraj Oberai, Apr 30 '21 at 15:39
facing the same error when starting widget tests on a real device — th_lo, May 06 '22 at 13:51

score 26 · Answer 1 · edited Jun 20 '20 at 09:12

26

Right now this issue is opened on github https://github.com/flutter/flutter/issues/32587

Temporarily you can solve this issue by switching to physical device instead of emulator How to test android apps in a real device with Android Studio?

Decision found on github (link upward)

I've got a temporary work around, which I can use for now. The exception above is thrown when I run the emulator as a Pixel 3 Android 9.+ Target (Q API). I made up a second emulated device, a Pixel 2 Android 9.0 Target (28 API), and this target works fine.

I'm also noticing that the Pixel 2 target takes up 8.5GB on Disk, while the Pixel 3 target only takes up 1.4GB. It makes me wonder if the Pixel 3 target is missing some important things.

edited Jun 20 '20 at 09:12

Community

1
1

answered May 13 '19 at 14:23

awaik

10,143
2
44
50

45

Switching to físicas device doesn’t work for me. I have same issue at iOS and Android physical devices and on iPhone emulator. – i6x86 Jun 12 '19 at 04:48
6

facing same issue on physical device, any resolution? – Sana.91 Oct 02 '19 at 12:47
1

try to use another emulator - for example create Pixel 3 Android 9 and try to execute app there. Also upgrade Flutter and if it is won't help try to run and check is everything is ok flutter doctor -v – awaik Oct 02 '19 at 20:22
but why facing issue on a physical android device: samsung ? – Sana.91 Oct 03 '19 at 08:50
@awaik asked this as a seperate question https://stackoverflow.com/questions/58215730/http-dart-httpexception-connection-closed-before-full-header-was-received – Sana.91 Oct 03 '19 at 09:05
same on windows – Amine Da. Sep 06 '22 at 17:39
I still get this error with my physical android mobile – BingLi224 Sep 21 '22 at 12:51

Vicky Salunkhe · Answer 2 · 2019-07-24T08:47:00.820

18

The issue is mainly with Android Q.

You can downgrade your android version from Android Q to Android Pie.

which eventually leads to resolve the issue.

edited Jul 24 '19 at 08:47

answered Jun 23 '19 at 20:54

Vicky Salunkhe

9,869
6
42
59

1

What about iOS? – Aniruddha Shevle Aug 01 '19 at 03:33
Sorry @AniruddhaShevle I don't have an iOS so have no clear idea about it. – Vicky Salunkhe Aug 02 '19 at 10:35
7

Not a solution, what if iOS? – Muhammad Faizan Jun 21 '20 at 06:21
happens on windows – Amine Da. Aug 24 '22 at 14:19

score 16 · Answer 3 · answered Jul 09 '19 at 10:58

No solution unless the Flutter guys fix it.

I'm having it on one machine (Mac OS Mojave) even when connecting physical iOS devices. Of course it happens too with emulated Android devices (no matter which one).

I've also having this problem in a different computer (MacOS Mojave too) with a physical Android device (with a very old Android version: 5.1).

flutter clean does not fix it at all in my case(s).

score 15 · Answer 4 · answered Jul 08 '19 at 21:14

15

First turning off your WiFi/Bluetooth.

And run below command:

flutter clean

And then quitting or restarting your emulator.

answered Jul 08 '19 at 21:14

Payam Khaninejad

7,692
6
45
55

3

This did not work for me: I've got a physical Android device working, but not the simulator, nor a physical iOS device, and the Android device in debug mode seems to work with or without WiFi/Bluetooth off. – nbloqs Jul 23 '19 at 22:21
@nbloqs closing wifi just makes sure that your open connection will be closed. – Payam Khaninejad Jul 25 '19 at 05:51
Thanks, but what I mean is that flutter clean does not fix this at all, independently of the WiFi/Bluetooth status. It really looks like a permanent problem, not something related to an open connection. – nbloqs Jul 25 '19 at 10:47
I had this issue in Visual Studio Code, So I turned off my Wifi, went to Terminal and `flutter clean` and then change Emulator device and again turned on the Wifi, issue resolved. – ArifMustafa Aug 02 '19 at 23:42
Thanks, im used: `flutter clean` them `flutter pub get` and finally `flutter run` – Lucas De Lavra Pinto Aug 24 '22 at 14:41

score 6 · Answer 5 · answered Jul 23 '21 at 06:45

6

This was my Problem And this worked For me:

PROBLEM
App would crash abruptly out of no where

CAUSE
I was using cached_network_image, When users uploaded heavy photos > 2MB, cache ran out of memory then app crashes. No warning.

SOLUTION
Use FadeInImage.memoryNetwork() or something else like NetworkImage() but not cache_network_image, it only works for less than 2 MB photos
thanks :)

answered Jul 23 '21 at 06:45

Ray Zion

610
10
11

1

We can use **placeholder: (context, url) => const CircularProgressIndicator(),** so the problem will solve with **CachedNetworkImage** – Adeel Nazim Nov 11 '22 at 16:42
1

@AdieRT I was using it still this issue happened. I recommend everyone to use this simple package which does not depend on many other dependencies: https://pub.dev/packages/cached_network_image_builder The only thing which you have to implement is when snapshot has an error and to delete the cached files after a certain period of time like 10 days or so to not clutter the device space... – SwiftiSwift Mar 08 '23 at 14:20
1

@RayZion Thank you for pointing this issue out! I wouldn't have known this... What I learned is to not depend on packages that much ... – SwiftiSwift Mar 08 '23 at 14:22

score 1 · Answer 6 · answered Mar 21 '21 at 19:43

In my case (error "HttpException: Connection closed before full header was received") the call was to an https address using Microsoft Internet Information Services as backend, in the SSL settings of the website in IIS i had mistakenly set "Client certificates: Accept" instead of "Client certificates: Ignore", setting "Ignore" solved the problem.

score 1 · Answer 7 · answered Mar 15 '22 at 12:45

1

I'm using Dio and faced the same issue so I have made this workaround by creating this interceptor which can be implemented too using the http interceptors.

You can check it here: https://stackoverflow.com/a/71415759/16314136

answered Mar 15 '22 at 12:45

Amr

148
7

score 1 · Answer 8 · answered Aug 19 '22 at 10:03

The issue was on the flutter code.the library socket_io_client it seems not to accept builder

OptionBuilder()
        .setTransports(['websocket'])
        .setPath('/messanging')
        // for Flutter or Dart VM

        //.setPath("/messanging")
       // .setExtraHeaders({"Authorization":"Bearer 
        ${datasource.user?.payload?.access_token}"}) // optional
        .build()

worked when i did use the below map method

socket = IO.io("http://10.18.5.212:3000/messanging", <String, dynamic>{
      "transports": ["websocket"],
      "Authorization":
          "Bearer eyJhbGciOiJIUzI1N......"
    }

score 0 · Answer 9 · answered Jul 25 '19 at 11:11

0

If you faced this issue on IOS build, follow th below steps

Goto Runner -> editSchema -> Run -> change build configurations to Debug.

if you are in Release mode you will face this issue, while running on android studio.

answered Jul 25 '19 at 11:11

Navin Kumar

3,393
3
21
46

score 0 · Answer 10 · edited Jul 17 '23 at 07:59

0

I've faced the same problem. Actually the problem was in the native code.

You can track the problem for android if you open an your_app/android project from Android Studio and run it.

The same for iOS -> open iOS project in Xcode So after I've fixed it the app run as intended

I hope this help

edited Jul 17 '23 at 07:59

אורי orihpt

2,358
2
16
41

answered Feb 07 '20 at 17:37

Vitaly Zeyenko

167
7

score 0 · Answer 11 · answered Feb 25 '20 at 12:21

0

I found the solution/work around. For me, it worked on physical device but not on emulator. The simple fix is to use your an emulator of x86 environment rather than x86_64 emulator.

answered Feb 25 '20 at 12:21

Axes Grinds

756
12
24

1

Release build will also have this issue on actual devices. – Purvik Rana Nov 05 '20 at 06:51

score 0 · Answer 12 · answered Mar 13 '20 at 03:11

0

I fixed the issue by setting request.persistentConnection = false; (default is true)

Writing this in case someone has the same problem...

answered Mar 13 '20 at 03:11

Bosko Popovic

157
2
9

where did you set this? – kishea Apr 30 '20 at 12:04
1

I extended the IOClient and done: class PersistentIoClient extends http.IOClient { static final http.Client _client = PersistentIoClient( HttpClient()..connectionTimeout = const Duration(seconds: 15), ); static http.Client get client => _client; static sync.Lock lock = sync.Lock(reentrant: true); PersistentIoClient([HttpClient inner]) : super(inner); @override Future send(http.BaseRequest request) async { request.persistentConnection = false; return await super.send(request); } } – Bosko Popovic May 01 '20 at 13:06
3

hi, @BoskoPopovic please write your code in a gist or github repo. I believe many people will need it, including me. Thank you – Dika Jun 04 '20 at 09:12
can anyone pls tell me more about this? @BoskoPopovic – Urvashi kharecha Jul 24 '20 at 05:19

Chris · Answer 13 · 2020-06-23T17:05:46.320

0

Like Vitaly says ..

I am also struggling to force this error at all when building through Xcode for iOS and I imagine the same goes for Android with Android studio..

For iOS do flutter build ios --release and then open/run the project in Xcode

For Android do flutter build apk --release and then open/run the project in Android Studio

It seems to be an issue when debugging through flutter ... I will update this answer if I find otherwise but it seems stable with this method

edited Jun 23 '20 at 17:05

answered Jun 23 '20 at 17:00

Chris

1,720
16
35

did you find any solution ? – hio Aug 19 '20 at 10:49
Hi, I think this is an issue only while debugging .. I don't actually think there is an issue when running in release mode – Chris Aug 19 '20 at 11:23

score 0 · Answer 14 · answered Oct 23 '20 at 06:57

I got the same error when I using Flutter with http package.

import 'package:http/http.dart' as http;
...
http.Response response =  http.get('url')

This was fine. But when I went to get the response.statusCode, it Error connecting error.

I found that I'm using SSR/v2Ray on my pc. I fix it by setting the proxy on Android Emulator extended controls panel.

score 0 · Answer 15 · edited Nov 03 '22 at 17:53

I was getting the same issue in POST request while sending the Images as multipart Resolved by using

contentType: MediaType('image', 'jpeg') in the http.MultipartFile

function

e.g

        request.files.add(
              http.MultipartFile(
                'image',
                stream,
                length,
                filename: basename(_image1.path),
                contentType: MediaType('image', 'jpeg'),
              ),
            );

where 'image' is the paramter name.

Don't forget to import 'package:http_parser/http_parser.dart'; for MediaType. Other Mediatype which you can use are

"image/png"
"image/jpg" 
"image/jpeg"

And I am sending this too in Header "Content-Type": "multipart/form-data"

score 0 · Answer 16 · answered Sep 14 '21 at 09:27

0

Stopping the running application and clicking on run again worked for me.

answered Sep 14 '21 at 09:27

Jagadish Nallappa

814
1
10
11

score 0 · Answer 17 · answered Nov 26 '21 at 04:34

0

You also need to mention your listening port which you define in your file like this final WebSocketChannel channel = IOWebSocketChannel.connect('wss://check.com:6043/');

It has solved my issue

answered Nov 26 '21 at 04:34

Dilendra Shahi

29
1

score 0 · Answer 18 · answered Jan 05 '23 at 12:45

0

Try using Uri.parse(url); Make sure the 'url' you put here is the full url with endpoint.

answered Jan 05 '23 at 12:45

Nandita Gandhi

51
4

How to fix HttpException: Connection closed before full header was received

18 Answers18

Linked

Related