Zwifi

@BowaDAO can you describe your setup a bit more so that I would be able to help? @Alfredoeb9 thanks for providing something that works around the issue in your case....

This library has not been designed for multiple processes being authenticated using the same session concurrently. In order for this to be successful, you'll have to be careful about how...

Re-hydrating the session from storage is actually based on the refresh token being present: the access token is short-lived, and it is a sensitive piece of data, so it isn't...

That's absolutely true, we are planning on a big refactor of this library to stop relying on the Access Token being issued by the OpenID Provider. When we do it,...

This is a feature we want to implement soon. I'll update this issue as it progresses.

There hasn't been progress on this yet, unfortunately we've had other features that took priority over this. In particular, there is a significant refactoring of the auth library we have...

Unfortunately, React-native is not currently supported by either libraries. It would probably be either to tweak the browser one than the node one to get there, but I suspect there...

No Inrupt library does at the moment, and I we won't be working on this soon unfortunately. I think @jaxoncreed was looking at this a while ago, but I don't...

Thanks for reaching out! Node 18 is not supported yet, which is why the `package.json` has the `engine` field setup the way it currently is. We are actively working on...

Hi @angelo-v, and thanks for the suggestion! We are looking at some internal refactoring to the auth library pretty soon though, so I'm not sure doing this now would be...