button isReady state

Question

button isReady state

Closed this issue 5 years ago · 9 comments

Hi,

After pairing the flic button the isReady becomes true as it should be. But the after i close the app and restart it again and connect to the button. I see that the function buttonIsReady is called but if i check button.isReady it stays false.

So isReady is only working the first time you pair the button after that it's always false and doesn't change anymore.

Answer 1 · 2020-01-13T16:54:15.000Z

Yes, you are in fact correct! I verified this now myself. I already know what the issue is, so I'll make sure to include a fix in the next release.

Thank you for reporting this!

/A

Answer 2 · 2020-01-14T07:05:11.000Z

Okey good to know. This also applies for android i think. But for now i fixed it by looking at connection state.

Answer 3 · 2020-01-14T09:57:23.000Z

Hi. What issues did you notice in the Android library? Anything regarding getConnectionState?

Answer 4 · 2020-01-14T10:02:56.000Z

Hi,

After pairing the flic button the isReady becomes true as it should be. But the after i close the app and restart it again and connect to the button. I see that the function buttonIsReady is called but if i check button.isReady it stays false.

So isReady is only working the first time you pair the button after that it's always false and doesn't change anymore.

Exactly this, but for now i've fixed it in my app by looking at connectionstate, that one is correct. So for the android lib isReady also stays false

Answer 5 · 2020-01-14T10:38:11.000Z

Hello. In the Android lib for Flic 2 there is no isReady, so could you please clarify or write the line of code that does not work?

Answer 6 · 2020-01-14T10:57:43.000Z

Thanks for the fast reply.

Oke i think i got confused because right now i'm working with both android and ios lib. There are some differences between the two. I was assuming that both work the same way. Is there a possibility that it could work exactly the same way? I can imagine this would be confusing for others to. This would help a lot when people are trying to get this working for both platforms.

Answer 7 · 2020-01-14T11:14:32.000Z

Yes, it is true that iOS and Android have some slight differences in behavior. On Android the "Ready" state is represented by CONNECTION_STATE_CONNECTED_READY in the connection state, while on iOS it is a separate property isReady.

I don't think this will be changed right now.

Answer 8 · 2020-01-14T11:20:16.000Z

Oke good to know thanks for the reply

Answer 9 · 2020-01-23T17:11:45.000Z

This should be fixed with release 1.0.2.