With the recent changes in upper management, give them time to work on things.

The last thing we want is another rushed app “update”.

In my experience management changes make very little difference to the pace of development.  We have been told the designers, developers and testers have been working on this for months and there are only so many hours in a day. If anything management changes tend to slow progress as staff attend corporate meetings to explain the new direction / priorities / re-organization  etc.    

Also,  They have known this feature would be missing from before they released this app 9 months ago - I hardly think you could refer to this solution as “rushed” ;-)

The outgoing folks made a major mess, then botched the recovery.

They made other (rumored) changes that made things worse.

They resisted the multiple calls to roll back to a working version.

They continued to flounder and fail to deliver a new working system to the point they were let go.

The new folks have no real option but to get a complete understanding of what is wrong, where the other teams are at in the recovery process and what needs to be done before issuing a lot of new orders and priorities.

Been in similar situations  multiple times and the ones that turned out well and were fixed the soonest all started by the new manager learning before issuing new orders. 

Never been in a $500 million hole myself but I can imagine the pressure and temptation to "do something" must be overwhelming, hope they resist and get to "do the right stuff" point before acting.