This week, I investigated and worked on a fix for a login UX bug that could leave users facing a blank page for a while. The issue was difficult to reproduce consistently, so my first step was to understand what happened during the login process.
Initially, I suspected a network problem. I inspected the browser’s Network tab while running the application locally and noticed that, during a first-time login, the system sent a request to a database address containing /null/.
After tracing the request, I found that the application was reading the database address from local storage—the browser’s storage for information saved between visits. During a first-time login, that value had not yet been saved. The application still attempted to use the missing value, resulting in the invalid /null/ address.
This appeared to be one possible cause of the blank page, although I had not confirmed that it explained every occurrence. To address this case, I added a check that immediately rejects the authentication attempt when the database address is missing, preventing the application from continuing with an invalid request.
Next week’s plan
Next week, I plan to temporarily pause the further investigation on login bug, as the issue is not critical. I will focus on a higher-priority task: migrating the existing tests from Jest to Vitest. Both tools run automated checks to help ensure the application behaves as expected. This work will involve updating the test setup, adapting existing tests where needed, and checking that they continue to run successfully in Vitest.
0 Comments