The reason for this behaviour is Locale, It sets the correct Locale. Set the local of your NSDateFormatter to en_US_POSIX will fix this. It works for both 24-hour and 12 hour format. On iPhone OS, the user can override the default AM/PM versus 24-hour time setting (via Settings > General > Date & Time > … Read more
The JavaScript runtime in React Native has access to date information just like any other environment. As such, simply: new Date() … will give you the current date. Here’s the MDN on working with dates in JS. If you want a good JS library to make working with dates even easier, check out MomentJS.
Don’t use NSTimer that way. NSTimer is normally used to fire a selector at some time interval. It isn’t high precision and isn’t suited to what you want to do. What you want is a High resolution timer class (using NSDate): Output: Total time was: 0.002027 milliseconds Total time was: 0.000002 seconds Total time was: … Read more
No need to remove the :’s. To handle the “00:00” style timezone, you just need “ZZZZ”: Swift let dateString = “2014-07-06T07:59:00Z” let dateFormatter = NSDateFormatter() dateFormatter.locale = NSLocale(localeIdentifier: “en_US_POSIX”) dateFormatter.dateFormat = “yyyy-MM-dd’T’HH:mm:ssZZZZ” dateFormatter.dateFromString(dateString) Objective-C NSDateFormatter *dateFormat = [[NSDateFormatter alloc] init]; dateFormat.locale = [[NSLocale alloc] initWithLocaleIdentifier:@”en_US_POSIX”]; NSString *input = @”2013-05-08T19:03:53+00:00″; [dateFormat setDateFormat:@”yyyy-MM-dd’T’HH:mm:ssZZZZ”]; //iso 8601 format NSDate … Read more
You’re overcomplicating things. NSDates don’t have time zones or calendars. [NSDate date] gets the current date, which is a measurement of a moment in history. If I run [NSDate date] in Europe at exactly the same time as you run it in America then we’ll get exactly the same value. How you print a date … Read more
[NSDate date] is a factory method for constructing an NSDate object. If you read the guide “Using Swift with Cocoa and Objective-C”, there is a section on interacting with Objective-C apis: For consistency and simplicity, Objective-C factory methods get mapped as convenience initializers in Swift. This mapping allows them to be used with the same … Read more
For simplicity I’m assuming that the dates you are formatting are all in the past (no “tomorrow” or “next week”). It’s not that it can’t be done but it would be more cases to deal with and more strings to return. You can use components:fromDate:toDate:options: with whatever combination of date components you are looking for … Read more
This may be useful for who want to use dateformatter.dateformat; if you want 12.09.18 you use dateformatter.dateformat = “dd.MM.yy” Wednesday, Sep 12, 2018 –> EEEE, MMM d, yyyy 09/12/2018 –> MM/dd/yyyy 09-12-2018 14:11 –> MM-dd-yyyy HH:mm Sep 12, 2:11 PM –> MMM d, h:mm a September 2018 –> MMMM yyyy Sep 12, 2018 –> MMM … Read more
You have a typo in your code: (last line should be setYear:) [components setDay:[day intValue]]; [components setMonth:[month intValue]]; [components setYear:[year intValue]];
I have a suspicion. Only a suspicion, but a pretty strong one. That value represents October 19th 2064. The Brazilian time zones observe daylight saving time starting at local midnight – that’s when their clocks go forward, so midnight itself doesn’t exist. October 19th is one of those transitions. Here’s some sample code using Noda … Read more