Stuck on retrieveServices (not connected after connection?)

[Silvesterrr]

Describtion
Hi, I've got this annoying bug it appears inconsistently every few times. It's really similar to this Issue [#402]
(#402)
It looks something like this:

• Connect do device
• Retrieve services -> and at this point the code hangs up
  I never found out this bug after first run of my app (first connect). Only at second, etc. connection.

I can't find any mistakes because one time it works like a charm and other time it has a problem.
I found out that disabling and enabling Bluetooth on the phone and retrying connecting works
(But I can't make my users to disable and enable Bluetooth. Or can I ;) ha-ha).

My code
I've tried writing my code in 2 ways both have this bug.

async function internalConnect() {
    await BleManager.connect(item.id);
    console.log('after conn');
    await BleManager.retrieveServices(item.id);
    console.log('after retrive');  // <---if the bug appears I never get to see this log
    await BleManager.write(
      item.id,
      global.GATTS_SECURITY_UUID,
      global.GATTC_ACCESS_CODE_UUID,
      stringToIntArray(code),
    );
    console.log('after write');
    await BleManager.read(
      item.id,
      global.GATTS_SECURITY_UUID,
      global.GATTC_ACCESS_CODE_UUID,
    )
      .then(readData => {
        console.log('access code response: ' + readData);
       //My other stuff here
      })
      .catch(error => {
        // Failure code
        console.log(error);
      });
  }

And this way:

BleManager.connect(item.id)
      .then(() => {
        console.log('connected to device');
        setTimeout(() => {
          BleManager.isPeripheralConnected(item.id, []).then(isConnected => {
            //do not remove
            if (isConnected) {
              console.log('Peripheral is connected!');
            } else {
              console.log('Peripheral is NOT connected!');
              Connect(); //<--- run the same function
              return;
            }
          });
        }, 900);
        setTimeout(() => {
          console.log('timeout');

          BleManager.retrieveServices(item.id)
            .then(PeripheralInfo => {
              console.log(PeripheralInfo);

              BleManager.write(
                item.id,
                global.GATTS_SECURITY_UUID,
                global.GATTC_ACCESS_CODE_UUID,
                stringToIntArray(code),
              )
                .then(() => {
                  console.log('written');
                  BleManager.read(
                    item.id,
                    global.GATTS_SECURITY_UUID,
                    global.GATTC_ACCESS_CODE_UUID,
                  )
                    .then(readData => {
                      console.log('access code response: ' + readData);
                      //My stuff here
                    })
                    .catch(error => {
                      handleConnectionErrors(error);
                      return;
                    });
                })
                .catch(error => {
                  handleConnectionErrors(error);
                  return;
                });
            })
            .catch(error => {
              handleConnectionErrors(error);
              return;
            });
        }, 900);
      })
      .catch(error => {
        handleConnectionErrors(error);
        return;
      });

In this way when the bug appears after running isPeripheralConnected I get Peripheral is NOT connected! So I've tried to resolve this by running this function again, but it just loops in this place and doesn't work.

How to Reproduce
Accually I don't know. It appears so random, I can't control it. I only know that it appears at second or next connections.

Smartphone:

• Device: xiaomi redmi note 7
• OS: android 10 QKQ1.190910.002
• react-native-cli: 2.0.1
• react-native: 0.66.4
• ble-manager: 8.0.1s

Btw, I really like this library. It's really intuitive :)

[michael-jogo]

@Silvesterrr any update on this?

[Silvesterrr]

@Silvesterrr any update on this?

Nope, am focused on something different...
But I'll be back onto it soon.
If I figure out anything new I'll post it.

[manxhong]

@Silvesterrr I had the same hanging issue with Android only, iOS works perfectly fine to me. There is a workaround I did that solves the issue. Try to createBond before the connect :

if (Platform.OS === 'android') {
   await BleManager.createBond(item.id);
  // you may want to add some delay after create bond
   await BleManager.connect(item.id);
}

Hope this helps.

[sarevok89]

Is there any update on this issue? I'm currently struggling with the same issue.

[sundayhd]

Same problem on xiaomi pad 5 😒

I tried so many things like clear bluetooth cache / binding etc.. I wasted few hours on this.

As workaround im wating at least 1 sec and if there is no connection (not getting "retrieveServices") I trigger disconnect and then reconnect again every time.
something like this (look at "handleHangOutBug" function):

const connectToDevice = async (id) => {
    try {
      await BleManager.connect(id);
    }
    catch(error) {
      handleError(error);
      return connectToDevice(id);
    }
    Log("Weight", "setDevice", "Connected to:", id);
    clearTimeouts();
    setConnectionStatus(1);
    currentDeviceId.current = id;
    retrieveServices(id);
    handleHangOutBug(id);
  }

  const handleHangOutBug = (id) => {
    hangOutTimeout.current = setTimeout(() => {
      if (connectionStatus.current === 1) {
        hangOutretries.current = hangOutretries.current + 1;
        isConnectingProcess.current = true;
        disconnect().then(() => {
          connectToDevice(id);
        });
      }
    }, (1000 + (hangOutretries.current * 250)));
  }

Please let me know if you have better solutions, thanks 😀

[sundayhd]

Toady I played with "bluetooth MAP version & AVRCP version" inside developer options.
When I changed map version to 1.3 its looks like that problem go away, so give it a shot 😃

[Silvesterrr]

Toady I played with "bluetooth MAP version & AVRCP version" inside developer options. When I changed map version to 1.3 its looks like that problem go away, so give it a shot 😃

yea, fun fact but I cannot force user to change that. Anyone tried using "react-native-ble-plx"?
Does this library has this issue?

[sundayhd]

Toady I played with "bluetooth MAP version & AVRCP version" inside developer options. When I changed map version to 1.3 its looks like that problem go away, so give it a shot 😃

yea, fun fact but I cannot force user to change that. Anyone tried using "react-native-ble-plx"?
Does this library has this issue?

I already tried ble-plx, same issue 😟

[RuchiraSwarnapriya]

Hi @Silvesterrr, I'm also facing similar kind of issue,
In very first time BleManager.connect return this error "Connection error" but if I try again it connected without any issue

Did you found a solution for this issue ?

[Silvesterrr]

Did you found a solution for this issue ?
Sorry I did not. I kinda hacked the way throught by disabling bluetooth and enabling it when the problem occures with other library. But I hope this issue will be resolved because it's so frustrating.

[JoshuaGuzman02]

Mismo problema, alguna solución?

[sfsnaruto]

Same issue

[KonstantinKostianytsia]

The same issue

[maeda-kazuya]

Same here, any solutions for this?

[sfsnaruto]

@maeda-kazuya , @KonstantinKostianytsia try to run the scan method first and then call the connect method.