search

kakzaki / blue_thermal_printer

Working with thermal printer via bluetooth (Flutter)
MIT License
164 stars 205 forks source link

Connection Refused #179

Closed luissouza closed 1 year ago

luissouza commented 1 year ago

Hello guys!!

I have a problem, the plugin finds the printer to connect, but when trying to connect it returns connection refused. Can you tell me what happens?

Im was trying with the version 1.0.9, because my application is old. Then, I updated to the last version 1.2.3, but i got the same error.

Thanks!

Logs:

**W/BluetoothAdapter(15659): getBluetoothService() called with no BluetoothManagerCallback
E/BThermalPrinterPlugin(15659): Connection refused
E/BThermalPrinterPlugin(15659): java.io.IOException: Connection refused**
E/BThermalPrinterPlugin(15659):     at android.net.LocalSocketImpl.connectLocal(Native Method)
E/BThermalPrinterPlugin(15659):     at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:290)
E/BThermalPrinterPlugin(15659):     at android.net.LocalSocket.connect(LocalSocket.java:130)
E/BThermalPrinterPlugin(15659):     at android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:367)
E/BThermalPrinterPlugin(15659):     at id.kakzaki.blue_thermal_printer.BlueThermalPrinterPlugin.lambda$connect$0$BlueThermalPrinterPlugin(BlueThermalPrinterPlugin.java:346)
E/BThermalPrinterPlugin(15659):     at id.kakzaki.blue_thermal_printer.-$$Lambda$BlueThermalPrinterPlugin$5PttsFOLL4334Mu9cVZiR79reKY.run(lambda)
E/BThermalPrinterPlugin(15659):     at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
E/BThermalPrinterPlugin(15659):     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
E/BThermalPrinterPlugin(15659):     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
E/BThermalPrinterPlugin(15659):     at java.lang.Thread.run(Thread.java:818)
github-actions[bot] commented 1 year ago

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.