Manage Application Configuration Using Global Settings

Hi Jason @wjgilmore,

Thanks a lot for the video! Great idea to store settings in the global collection. I wish we could have something built-in soon!

Question: do you update logged-in user immediately after signing up a new user?
If yes, then could you please clarify if the long-existing bug/feature with the logged-in user record usage immediately (same screen) after signup is fixed?

There is a long-existing issue with conditional actions usage after signup/login (starting even from here Problem restricting users without access code - #4 by Victor - see explanation by ex-Adalo employee Ashley). Apparently due to some internal logic (I suspect some kind of racing condition while processing token) the subsequent conditional actions can not recognize just logged-in user, and sometimes do not work correctly.

Empirical rule of thumb is “do not use conditionals after signup/login”. So for example if there is a user with “isAdmin” boolean property and we need to direct them to specific Admin screen, we can’t do it in the action sequence after signup or login; we need to have a separate “routing” screen for that.

So my question is if this bug still exists and if yes, could it happen with updating logged-in user? I can’t check in any of my apps because I have removed all actions to separate screens :slight_smile: .

Best regards, Victor.