software56Q: Problem with login
I did observe this before but since now its becoming a pain, I have to ask this. Why is there a problem with the delivery of the login OTP to my non-google email address (email I used to create my account)? Your OTPs are not getting delivered and even when they do and we input the OTP there is a error message ('Something went wrong'). Cant you simply give the option to login with an email and a password instead of OTP? Also while I was testing I observed that when the initial code runs into errors, it automatically starts its next journey to weed out the errors and consumes extra credits. It happened with one of my projects where 100 credits were used on a loop without having the option to stop further debugging. Am I missing something or should there be a 'stop' button?
Shubham_Questera
Jul 1, 2025A: We are looking into figuring out a better OTP provider. A lot of domains are blocking out current provider. To maintain high security, we are not adding passwords right now but maybe in the future.
When there is an error and it automatically starts to fix them, it DOESN'T consume extra credits. We will add a stop button there as well soon.