Hello, I'm developing an app that relies on date calculations and the iOS 11 simulator displays wrong clock, with two hours shift (I think it's displaying UTC hour instead of local)
Also, when using data calculations, differences between dates are wrong. I am missing something? Is there any internal change that's doing this?
Any idea would be appreciated, thanks.
Did you check data/time in the sim's settings? Location via the simulator's debug menu?
What is the time zone on your computer?
Any update to this? Any trackion on the bug report? Seems to be still an issue in the GM of tvOS and Xcode 9.
My Location under Simulator Debug is None, my time zone is 4 hours behind UTC +0000, no issues, works as expected for the latest sim & xc9 builds.
print (Date())
2017-09-17 05:09:00 +0000Yeah, you'll get UTC as the timezone when using older runtimes on High Sierra. I believe the same is true with iOS 11 on Sierra.
That's correct. I get UTC timezone in the simulator if I run an iOS 10 simulator. The iOS 11 simulator works as intended.
I am on the full release (downloaded from the app store) of XCode 9, running Mac OS 10.13, iOS 10. My Simulator time is off 4 hours from my system time. Under iOS 11 it works fine.
Yes. That is correct. You're stuck with UTC for older simulator runtimes.
For what it's worth, the iOS 10 simulator on my machine shows UTC on the clock, but actualy uses my timezone internally. This just has thrown me off track two hours today.
Cheers
I have been battling with constant requests to logon to my AppleId on my iOS 10 and iOS 9 simulators so I can test iCloud integration for my apps. The time on the simulators is set to UTC as stated in this thread.
I am astonished that the response from Apple is essentially "too bad". This effectively makes my testing on simulators totally useless.
The response from Apple should have been "we will get this fixed ASAP!!!".
I agree with @markhess.
Just got a new MacBook Pro with High Sierra. We work with a pretty large system that can't just suddenly make transaction to XCode 9 nor just cut support for iOS 8/9/10. Now the simulator debugging is pretty much useless.
The level of arrogance and quite frankly shortsightedness (that's the nicest word I can use) of this response is staggering. This is like a development 101 screwup. I spent multiple hours today working on something just to find this thread for a very stupid problem. This decision leaves running the simulator completely worthless.
Hello there, please: can you fix this?
