Does hooks need initConnection?

[jeremyhalin]

I'm experiencing errors like Not initialized, Please call initConnection() whereas I use hooks and have version 7.
I have a lot of errors in production, but absolutely none on an emulator or on my device in debug mode.
I don't really understand where all those errors are coming from.

Anyone using hooks and having zero error?

[jeremyhalin]

I'm bumping my question. I'm still getting A LOT of errors about Not initialized, Please call initConnection().
Do I need to use connected from hooks to know if I'm connected or not before doing anything?
What happens if connected is false? How to connect again? Does it happen automatically?
To be honest, I'm thinking about going back to class component just for the shop part of my app because it was working well this way. Since I switch to hooks, I have so many errors.

[jeremyhalin]

I don't get the point of connected in hooks then.

[Arjan-Zuidema]

connected seem to be a state variable to check if the module is connected. I would guess it's something like this

const [connected, setConnected] = React.useState(false)

React.useEffect(() => {
  initConnection().then(() => {
    setConnected(true);
  });

  return () => {
    endConnection()
  }
}, [])

[Arjan-Zuidema]

Also, I think you cannot use getSubscriptions/getProducts before connected === true

[SebastianMieszczanczyk]

You don't need to initialize connections on your own when you use the hook. As it was said above - use only methods that are exposed from the hook. It works correctly for me. Connected is just a state variable, so you can just use:

React.useEffect(() => {
if (!connected) {
   // refresh to initialize
   return;
}
// here you can do your steps after connection is established
}, [connected])

[SebastianMieszczanczyk]

So relying on code as on Promise (code in the answer above) is not correct.