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.

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

windows ping release #22

Closed
m2faridi opened this issue Mar 24, 2022 · 6 comments
Closed

windows ping release #22

m2faridi opened this issue Mar 24, 2022 · 6 comments

Comments

@m2faridi
Copy link

hi
windows app release show console application
for debug is good
pls fix this bug

@ZoubairDaddow
Copy link

also for me

image

@point-source
Copy link
Owner

I don't understand what you are asking. What is the behavior you are experiencing to see?

Have you read the windows section of the readme?

@ZoubairDaddow
Copy link

When we use dart_ping in windows and build the application using
flutter build windows
the ping window appears (just in release mode)
when we run in debuge mode it doesn't appear

@ZoubairDaddow
Copy link

When we use dart_ping in windows and build the application using flutter build windows the ping window appears (just in release mode) when we run in debuge mode it doesn't appear

dart_ping: ^6.1.1

Doctor summary (to see all details, run flutter doctor -v): [√] Flutter (Channel stable, 2.10.3, on Microsoft Windows [Version 10.0.19042.1266], locale en-US) [√] Android toolchain - develop for Android devices (Android SDK version 31.0.0) [√] Chrome - develop for the web [√] Visual Studio - develop for Windows (Visual Studio Enterprise 2019 16.11.8) [√] Android Studio (version 2020.3) [√] VS Code (version 1.65.2) [√] Connected device (3 available) [√] HTTP Host Availability

@m2faridi
Copy link
Author

m2faridi commented Apr 7, 2022

pls fix this bug

@point-source
Copy link
Owner

point-source commented Apr 17, 2022

Guys, this is covered in the Windows Compatibility section of the readme (on both github and pub.dev) and there is a workaround there. This is a flutter bug, not a dart_ping bug and there is nothing I can do to the dart_ping package to prevent it. You need to apply the workaround in every flutter app you use this library with. That's why it's in the readme.

I'm closing this issue since there is a documented fix available that I have verified to be working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants