Am getting "The current user has been blocked" when trying to connect to cloud console

Was working on my app FLUTTER WEB APP, and suddenly, I have been blocked.... What can I do ? When I try to sign in to the console, I get "The current user has been blocked"... I need to continue working on app as I have a deadline coming up...

TL;DR

User is repeatedly encountering the "The current user has been blocked" message on cloud console. Support team fixed the false positive issue, unblocking the account. Upgrading to Pro may help avoid similar problems in the future, as there are limitations based on the project's age and subscription level. The support team will need time for a long-term solution.

Please share your project id

Here it is : 69a842e8001261bf62f1

Here is its : 69a842e8001261bf62f1

Any idea why it's doing that ?

Is everything ok ?

am kinda getting worried about all this

Am sorry to ask again - it's getting late where I live (France) and tomorrow morning must show app to some collegues. Is there a way to solve my problem ?

We rolled out some abuse detection, but it caught yours as a false positive. I've unblocked your project and account

Ok thank you. Got me worried. Could this happen again ?

we've fixed the false positive issue so it shouldn't happen again...unless you do something suspicious

What is « something suspicious » ?

Very urgent - the situation is still the same. Account is still blocked.

I still get "The current user is blocked"

"has been bocked"``

Hey, please check again now

It's working

do you think it will stay that way ?

I can sign in to console fine

<@462046107556511744> can look into it more deeply later-on, to better understand what's triggering it. Till then, I dont think I can promise threat protection wont kick in again. That said, I can see multiple limitations based on age of the project, and if it's Free, Pro, or Scale.

Not sure if you have Pro, but if not, it might be worth upgrading for a month. It sounds like very shady sales tactic, plus I cannot even guarantee having Pro will fully resolve it... So take this suggestion with a grain of salt, from engineer looking at code, just trying best to minimalize problem possibility, considering your urgency.

Support team is best to resolve this long-term, but that might take a day or few to get 100% resolved

Thank you very much for your help - will keep everyone posted to let you know if problem pops up again. I promise I am not doing any suspicious activities 😉 Apparently Steven thought they had managed to solve the false positive pb

did it work and then stop working?

I don't know - I had'nt had time to check right away when you first did something. But when I tried to sign in to console the next day, had the same pb