We are now getting "400" errors (such as the one below) when requesnt an avatar with a valid user_id after successfully generating and using an access token for a federated app id. This is in apps that have already been released for a while and used to work, as welss as any in our dev environements. This is a big problem for our existing clients, and also delays our development for enar term releases. In the past there have been Meta backend issues that temporarily caused this and eventually the problem went away. Is that the case now? If not, can someone please help me understand and mitigate whey this is now happening for all of our federated apps?
This seems to have resolved itself as it has in the past, but we and our clients were without federated app avatars for several days. Can someone at Meta please tell us what occured and how we might detect it / report it, so that we can give our clients a heads up (and avoid our developers spending time trygin debug it before realizing it's not our regression)?
We re now having this problem again for the last few days, and it is not resolving itself. However, even if it someone corrects itself again, we need to hear from Meta dev team on what is causing this. We are once again unable to provide our services to our users, and have no explanation why. I see similar threads where mulitple people complain about this, and thereis no response from Meta and then the system eventually corrects itself. Please let us know what we shoudl do or when the problem will be resolved if it is a Meta server issue. At this point it is creating great risk to us as a business, and we may lose out on major dus dev opportunities that can be detrimental to our ability to move forward as a company. Here are other examples from the forum: https://communityforums.atmeta.com/t5/General-Development/Meta-Avatar-load-fails-with-Failed-to-retr...
