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
It appears this happens because these are all authenticated routes, and on initial load, user is not yet authenticated. Since I'm handling auth logic through Tracker Autorun, the container component is attempting to load these subscriptions, but they are returning undefined, causing an error in the browser console:
Is there any way to prevent this error from being logged? This happens not only for anonymous users, but also when a user logs out.
The text was updated successfully, but these errors were encountered:
Looking at the code, it appears its just a console log, and not an actual error going on. Perhaps it would just be best to eliminate the console.log, as it's not really needed?
function errorHandlingLogic (err) {
console.log("Error invoking SubsManager.subscribe(%s): ", sub.identifier , err.reason);
// expire this sub right away.
// Then expiration machanism will take care of the sub removal
sub.updated = new Date(1);
}
I receive this error when listening to subscribe within react-komposer onChange, for example:
It appears this happens because these are all authenticated routes, and on initial load, user is not yet authenticated. Since I'm handling auth logic through Tracker Autorun, the container component is attempting to load these subscriptions, but they are returning undefined, causing an error in the browser console:
Is there any way to prevent this error from being logged? This happens not only for anonymous users, but also when a user logs out.
The text was updated successfully, but these errors were encountered: