It depends. Some other reasons:
1. It's an enterprise product and the economic buyer doesn't know or care about bugs as much as checklisted features.
2. The company is not connecting the impact of fixing bugs to their bottom line. Or they are and estimate the impact to be low.
3. The code base is due for a rewrite so it would be a waste.
4. It's a side bet not worth the extra resources.
For all the phone developers out there:
5. Fixing a bug means you have to go through a re review of your marketing assets that haven't changed in 3+ years and there's a non zero chance each time your review could result in _your app being removed from the storefront_ and losing _days_ of revenue after you appease whatever whimsical issue wasn't an issue the hundreds of times you've submitted previously and wait for the next review slot.