Accounts.createUser -> Meteor.logginIn issue

[copleykj]

Accounts.createUser when called from the client currently sets Meteor.loggingIn to true even if createUser fails and throws an error. This causes applications that use the Meteor.logging in to display a loading page to re-render their template potentially causing loss of form values and validation errors displayed.

My personal thinking is that Meteor.loggingIn should not enter a true state unless account creation is successful.

[glasser]

The whole purpose of loggingIn is to be true while the login method (and createUser is a login method) is running, so this would defeat the point of uses loggingIn. Note that createUser is not a two step "create user then log in" process: it's just one round trip.

[dburles]

What's the solution?