Assets and areas are not always populated on login

[alexadamsmith]

This bug only occurs after clearing caches on the browser or doing a fresh install in Android. I log in for the first time, then click "create log" in the AllLogs view to navigate to the EditLog view. Even though I'm logged in, the areas and assets haven't been populated.

Curiously, if I do the same thing (log in after a fresh install / cleared caches) and then use the app shell menu to navigate to the EditLog view, then the problem does NOT occur, and areas and assets are populated!

In an email exchange, @jgaehring suggested we should request assets and areas whenever /logs/edit is loaded.

[alexadamsmith]

More exactly:
The error occurs only when the user first navigates to the 'edit logs' view, THEN logs in, and is re-directed back to 'edit logs'. Looking at it a bit more, I believe this occurs regardless of whether they are navigating to 'new logs' via the menu, or via the 'create log' button.

[alexadamsmith]

I fixed this by loading assets and areas when a /logs/edit route is called, rather than when /logs is called. On /logs, we now only load logs and user data + site info.

[jgaehring]

Excellent! Glad you were able to figure that out! 👏 👏 👏

[mstenta]

(Transferring all issues from old repository. See #92)

[jgaehring]

Closing this per Alex's comment above