That does not answer the question. I know it's wrong, and I've pointed it out to the development team who coded it. What I'm looking for is a way to get the simulator to behave like a device in order to be able to trap such things with unit tests. Maybe there's some other code somewhere in the app that has a similar issue. It won't be caught by unit tests running on a simulator unless we can somehow set the simulator to behave the same way.
The docs say that it uses the locale setting, so maybe there's a way to set the locale to mimic what I described in my original post. What I've tried doesn't work, though.
Topic:
App & System Services
SubTopic:
General
Tags: