We need to be open and honest about the possibility that our code may act in ways we don't foresee.
Not hitting a bug is not the same as not having a bug. I'd bet money that whatever system you're talking about has bugs. Plus, the system may be far simpler than you assume.
Part of it is cost/benefit ratio for the extra effort, part of it is market demands, part of it is lack of technology, part of it is unavoidable stuff like the halting problem.
It's also worth remembering that Signal is developed by a non-profit with a total of 36 staff members (if Wikipedia is correct). That means they have fewer developers, and even fewer Android developers.
If you think it's so easy, be your own change and do it, and then we can judge the results.
> If 36 people and $100 million in funding is not enough to make a messaging app that doesn't suck, what _is_ required and why is it more than that?
You're assuming there's a solution of a certain form to get you what you want, but maybe it's your assumption that's wrong.
I mean, there are formally verified systems that might be like what you're asking, but they're both 1) very expensive, 2) extremely feature poor.
If they do, they're either incompetent, lying, or building something enormously expensive yet completely impractical for most if not all real world uses.