> We are now well aware of the problem and have since submitted a version that fixes the problem for the vast majority of users.
Well, you either found the problem and fixed it or you fixed something and now hoping it was what was crashing your app. Or you have multiple crash points in the app. If it still crashes - fine, you have more work ahead of you. Just don't try and twist words to make things look better than they are.
I can only laugh at this comment "don't try and twist words to make things look better than they are". Not twisting words, it's pretty straight forward.
Comments
> We are now well aware of the problem and have since submitted a version that fixes the problem for the vast majority of users.
Well, you either found the problem and fixed it or you fixed something and now hoping it was what was crashing your app. Or you have multiple crash points in the app. If it still crashes - fine, you have more work ahead of you. Just don't try and twist words to make things look better than they are.
I can only laugh at this comment "don't try and twist words to make things look better than they are". Not twisting words, it's pretty straight forward.
Well, does your updated version still crash once in a while?