You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 22, 2019. It is now read-only.
I've noticed that if meteor login token expires (user doesn't use the app for too long), Meteor.connect() function is not calling the callback.
The problem seems to be inside DDPExtensions.swift, resume(url: String, callback: DDPCallback?) function. Result of self.loginWithToken() call is not being used and, if it's false, callback is never called.
Looking at the code, seems like callback is also not being called if self.loginWithToken()'s callback gets error passed in.
We are currently testing a fix for this issue, I will submit a pull request once we're done.
The text was updated successfully, but these errors were encountered:
yvdorofeev
added a commit
to yvdorofeev/SwiftDDP
that referenced
this issue
May 7, 2017
I've noticed that if meteor login token expires (user doesn't use the app for too long), Meteor.connect() function is not calling the callback.
The problem seems to be inside DDPExtensions.swift, resume(url: String, callback: DDPCallback?) function. Result of self.loginWithToken() call is not being used and, if it's false, callback is never called.
Looking at the code, seems like callback is also not being called if self.loginWithToken()'s callback gets error passed in.
We are currently testing a fix for this issue, I will submit a pull request once we're done.
The text was updated successfully, but these errors were encountered: