No, well it depends on how they handle errors. Not all apps are stupid enough not to handle errors and crash. YOu can not make blanket statements, that is why you are being modded down. You can not speak for all apps, and it makes you sound childish to do so.
Are you telling me you'd wrap a System.out.println() in a try/catch? Even that's not absurd enough to exemplify the problem that all of you are clearly having in comprehending the magnitude of the absurdity you're spouting. The program is GUARANTEED the permission. Why would there be code to check to see if it has the permission? Do you people even understand the current Android permission model? (Such a function literally does not exist in the API.)
It's like a huge joke that I'm the punch line of. And surely, you're not recommending that a tiny fraction of apps not crashing excuses the fact that such a change would break undoubtedly near 100% of applications.
I'm just enraged at the fact that everyone is making caveats to try to make me look wrong while not a single person has actually addressed the claims I'm making. Actual Android developers in #android agree with me - not only that this would be bad for legacy apps, but that it would almost guaranteedly cause them to crash because they WOULDN'T HAVE CODE to check to see, because THAT DOESNT EXIST in the Android API because the manifest ensures they have that permission.
