Vit Horacek
Vit Horacek
This needs better error handling, when the card is deactivated we send the onyx update to remove the card, but it might take longer so the user was still able...
@koko57 would you be able to look as well? I can see that the updates are being queued to remove the card from Onyx, but it seems like it's not...
If you find this needs to be addressed in BE, then please ping me in slack 🙌
From the [logs](https://www.expensify.com/_devportal/tools/logSearch/#sort=asc&size=10000&query=request_id%3A%228d0cd0bc3848799c-BKK%22%20AND%20timestamp%3A%5B2024-10-10T00%3A00%20TO%202024-10-15T23%3A59%5D), its because the account does not have the legal first name set, but I think we do not have this restriction when creating a new virtual card....
The problem here is that the card was in a deactivated state when you tried to get a new one; they took the action very fast, so the pusher update...
I think we should do the same as when creating the card and show a spinner when the replacement card is requested until we get a response and then show...
I will try to handle the errors nicer in backend
Still on my list
Started a draft, will need to test more