Resolved, but can still affect customers for up to 4 hours...

So many problems here, and no signs of an updated SDK that behaves properly on malformed input.

> Accrescent is the end goal for a secure and private app store but it's still in alpha

Note that nobody (new) can submit to it today; the developer console HTTP 503s and is only available to an allow-list of developers.

Accrescent has been quiet for a while, but had claimed in the past they would open the store up for new submissions again soon, it will perhaps happen by the end of the year. Its self-imposed requirements for this are to provide a better developer experience and more common app store features developers (should) expect. They recently announced they will be posting more about the progress made towards such goal, after the big announcements and releases of some months ago.

I'm more worried about the lack of a police to take apps down when it is very clear they should not be there. This is a present problem, presently solvable and that is not acknowledged despite the fact it harms the user.

Yes, and the UK's industry body - Rail Delivery Group - has thoroughly screwed up distribution of the timetable data for this trial... so no online retailers (with the exception of BR Fares) will be selling tickets for the operation. Hardly a fair trial.

Issues seems to be completely broken, just getting unicorns.

Interestingly the API still works for creating an issue (but webhooks weren't fired).

They've also started revoking previously valid tokens. I can no longer use RedReader with the API client I had created for this purpose.

The only winning move now is to start impersonating their app.