The State Changers went through a debugging process of an authentication issue with a user's token in a Xano-based application. George explained that a function was working inconsistently, with the function attack breaking sometimes and working at other times. This inconsistency appeared connected to whether the token was obtained during a new user's sign up or during a user login.
The State Changers identified a problem with the workflow, where the application assumes the presence of a 'firm' each time it runs, which wasn't always the case. To prevent the application from breaking due to the absence of a 'firm', the State Changers used an 'if - then' statement to run checks and added logging mechanisms.
The State Changers experienced errors while trying to run these checks and logging functionalities, requiring them to refine their error handling approach several times.
The tokens being generated didn't contain valid user IDs. Instead, they defaulted to zero - causing the function to fail when utilizing those tokens - the discovery resulted in understanding the actual cause of the inconsistency.
In the end, the issue was traced to the 'sign up user' part of the User Management subsystem. The bug was in the token generation process. A new token was created but wasn't properly processed to include the correct user ID, which eventually led to the function issues.
The debugging process centered on creating more robust error handling, using methods such as run debugging, adding error logging to tables, testing application performance in different environments, and analyzing code in areas related to where the issues were found.
(Source: Office Hours 2/10 )