Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-45304

Android: QBluetoothSocket::abort() should not always return Unconnected immediately

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P3: Somewhat important P3: Somewhat important
    • None
    • 5.5.0 Alpha
    • None
    • Android

      As a result of fixing QTBUG-44930 it is possible to receive an Unconnected signal right after an QBluetoothSocket::abort() while the socket is still being opened. The QBluetoothSocket should remain in Closing until the WorkerThread has really finished.

      This use case can only triggered when the internal InputThread has not been started and abort() is called.

      Two scenarios need to be considered. The running QBluetoothSocket.connect may fail or connect. It it fails the Unconnected() state should be set. If it succeeds the closeJavaSocket() signal should be emitted. Once the Thread has finished the Unconnected state should be set.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            ablasche Alex Blasche
            ablasche Alex Blasche
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                There are no open Gerrit changes