So I’ve been using the @meteorrn/core library on a production app; it’s a great library and a good translation of Meteor on a RN environment. But something that users notice me constantly is that after they exit the app (not closing it) and reopen it, they can’t call the subscriptions nor the methods of the server.
After some logging I found out that the app does connect to the server and it still keeps the token and the user, but the server logs out the user between that time frame so there’s this conflict of the client having the user logged in and in the server is not.
I’ve done various solutions like calling directly Meteor._loginWithToken, ditch the autoReconnect flag and use a custom reconnection process with useEffect, etc. But none of them helped me to fix this issue so I think that I’m not using a correct process or ignoring something important.
Have any of you encountered with something like this? And if so, what did you do to fix it? I feel like I’m still new in the Meteor environment so I’d like to hear your opinions and experience
While writing this I just found out this post that had the exact problem that I have but with facebook tokens and the first major version of react-native-meteor in 2016. It’s not the same codebase on any of the libraries and it’s not the same log in method but I add it to give a little bit of context respect the ‘server logging out the user’ part User logged in on client, but not on server (React Native)
The React Native package doesn’t have a large amount of support and I’ve gotten into just changing the package to make it work better for me.
Personally I’ve been using this commit in my package.json and it has generally been good:
But note, I use only a subset of the features of Meteor, so I’m not making any promises about everything working. This is definitely an issue with the react-native package itself and not Meteor
