UIDatePicker shows incorrect time












1















I'm trying to set the minimumDate to the datepicker, but the datepicker adds +1 hour when showing.



I suspect that the timezone of the Datepicker is different from firstPossibleOrderTime.



I get this from api: 20181127151122.



Then use SwiftyDate pod to init date.



    DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss",
region: .currentIn()).

let datePickerFrame = UIDatePicker(frame: .zero)
datePickerFrame.locale = Locale.init(identifier: "nb")


print(self.firstPossibleOrderTime.date)
print(self.firstPossibleOrderTime.date.add(28.days))

datePickerFrame.minimumDate = self.firstPossibleOrderTime.date
datePickerFrame.maximumDate = self.firstPossibleOrderTime.date.add(28.days)


How can i prevent the Datepicker from increment the time by 1 hour?










share|improve this question

























  • What is firstPossibleOrderTime.date value? How did you init it? Is it the correct value?

    – Larme
    Nov 27 '18 at 13:34











  • Can you show us what 'firstPossibleOrderTime' is ? My guess is when your timestamp comes from the server and you parse it into a date instance you are using the wrong format (eg. timezone)

    – Teetz
    Nov 27 '18 at 13:34













  • I get this from api: 20181127151122. Then uses pod to init: DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss", region: .currentIn()). self.firstPossibleOrderTime.date is then: 2018-11-27 15:11:22 +0000

    – Krister Moen
    Nov 27 '18 at 13:43













  • @KristerMoen You can edit your question to add these informations to your question. Also the information which pod you are using is important thou.

    – Teetz
    Nov 27 '18 at 13:46
















1















I'm trying to set the minimumDate to the datepicker, but the datepicker adds +1 hour when showing.



I suspect that the timezone of the Datepicker is different from firstPossibleOrderTime.



I get this from api: 20181127151122.



Then use SwiftyDate pod to init date.



    DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss",
region: .currentIn()).

let datePickerFrame = UIDatePicker(frame: .zero)
datePickerFrame.locale = Locale.init(identifier: "nb")


print(self.firstPossibleOrderTime.date)
print(self.firstPossibleOrderTime.date.add(28.days))

datePickerFrame.minimumDate = self.firstPossibleOrderTime.date
datePickerFrame.maximumDate = self.firstPossibleOrderTime.date.add(28.days)


How can i prevent the Datepicker from increment the time by 1 hour?










share|improve this question

























  • What is firstPossibleOrderTime.date value? How did you init it? Is it the correct value?

    – Larme
    Nov 27 '18 at 13:34











  • Can you show us what 'firstPossibleOrderTime' is ? My guess is when your timestamp comes from the server and you parse it into a date instance you are using the wrong format (eg. timezone)

    – Teetz
    Nov 27 '18 at 13:34













  • I get this from api: 20181127151122. Then uses pod to init: DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss", region: .currentIn()). self.firstPossibleOrderTime.date is then: 2018-11-27 15:11:22 +0000

    – Krister Moen
    Nov 27 '18 at 13:43













  • @KristerMoen You can edit your question to add these informations to your question. Also the information which pod you are using is important thou.

    – Teetz
    Nov 27 '18 at 13:46














1












1








1








I'm trying to set the minimumDate to the datepicker, but the datepicker adds +1 hour when showing.



I suspect that the timezone of the Datepicker is different from firstPossibleOrderTime.



I get this from api: 20181127151122.



Then use SwiftyDate pod to init date.



    DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss",
region: .currentIn()).

let datePickerFrame = UIDatePicker(frame: .zero)
datePickerFrame.locale = Locale.init(identifier: "nb")


print(self.firstPossibleOrderTime.date)
print(self.firstPossibleOrderTime.date.add(28.days))

datePickerFrame.minimumDate = self.firstPossibleOrderTime.date
datePickerFrame.maximumDate = self.firstPossibleOrderTime.date.add(28.days)


How can i prevent the Datepicker from increment the time by 1 hour?










share|improve this question
















I'm trying to set the minimumDate to the datepicker, but the datepicker adds +1 hour when showing.



I suspect that the timezone of the Datepicker is different from firstPossibleOrderTime.



I get this from api: 20181127151122.



Then use SwiftyDate pod to init date.



    DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss",
region: .currentIn()).

let datePickerFrame = UIDatePicker(frame: .zero)
datePickerFrame.locale = Locale.init(identifier: "nb")


print(self.firstPossibleOrderTime.date)
print(self.firstPossibleOrderTime.date.add(28.days))

datePickerFrame.minimumDate = self.firstPossibleOrderTime.date
datePickerFrame.maximumDate = self.firstPossibleOrderTime.date.add(28.days)


How can i prevent the Datepicker from increment the time by 1 hour?







swift timezone uidatepicker






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 27 '18 at 14:26







Krister Moen

















asked Nov 27 '18 at 13:26









Krister MoenKrister Moen

1939




1939













  • What is firstPossibleOrderTime.date value? How did you init it? Is it the correct value?

    – Larme
    Nov 27 '18 at 13:34











  • Can you show us what 'firstPossibleOrderTime' is ? My guess is when your timestamp comes from the server and you parse it into a date instance you are using the wrong format (eg. timezone)

    – Teetz
    Nov 27 '18 at 13:34













  • I get this from api: 20181127151122. Then uses pod to init: DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss", region: .currentIn()). self.firstPossibleOrderTime.date is then: 2018-11-27 15:11:22 +0000

    – Krister Moen
    Nov 27 '18 at 13:43













  • @KristerMoen You can edit your question to add these informations to your question. Also the information which pod you are using is important thou.

    – Teetz
    Nov 27 '18 at 13:46



















  • What is firstPossibleOrderTime.date value? How did you init it? Is it the correct value?

    – Larme
    Nov 27 '18 at 13:34











  • Can you show us what 'firstPossibleOrderTime' is ? My guess is when your timestamp comes from the server and you parse it into a date instance you are using the wrong format (eg. timezone)

    – Teetz
    Nov 27 '18 at 13:34













  • I get this from api: 20181127151122. Then uses pod to init: DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss", region: .currentIn()). self.firstPossibleOrderTime.date is then: 2018-11-27 15:11:22 +0000

    – Krister Moen
    Nov 27 '18 at 13:43













  • @KristerMoen You can edit your question to add these informations to your question. Also the information which pod you are using is important thou.

    – Teetz
    Nov 27 '18 at 13:46

















What is firstPossibleOrderTime.date value? How did you init it? Is it the correct value?

– Larme
Nov 27 '18 at 13:34





What is firstPossibleOrderTime.date value? How did you init it? Is it the correct value?

– Larme
Nov 27 '18 at 13:34













Can you show us what 'firstPossibleOrderTime' is ? My guess is when your timestamp comes from the server and you parse it into a date instance you are using the wrong format (eg. timezone)

– Teetz
Nov 27 '18 at 13:34







Can you show us what 'firstPossibleOrderTime' is ? My guess is when your timestamp comes from the server and you parse it into a date instance you are using the wrong format (eg. timezone)

– Teetz
Nov 27 '18 at 13:34















I get this from api: 20181127151122. Then uses pod to init: DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss", region: .currentIn()). self.firstPossibleOrderTime.date is then: 2018-11-27 15:11:22 +0000

– Krister Moen
Nov 27 '18 at 13:43







I get this from api: 20181127151122. Then uses pod to init: DateInRegion(firstPossiblePickup, format: "yyyyMMddHHmmss", region: .currentIn()). self.firstPossibleOrderTime.date is then: 2018-11-27 15:11:22 +0000

– Krister Moen
Nov 27 '18 at 13:43















@KristerMoen You can edit your question to add these informations to your question. Also the information which pod you are using is important thou.

– Teetz
Nov 27 '18 at 13:46





@KristerMoen You can edit your question to add these informations to your question. Also the information which pod you are using is important thou.

– Teetz
Nov 27 '18 at 13:46












1 Answer
1






active

oldest

votes


















0














I guess that probably you are using the wrong date formatter to convert the date you are receiving from the server.

Is the time you receive from the server a string?

If it is a string, in which time zone is set?

You must take that into account before parsing it, usually servers returns a en_US_POSIX date string that you can parse with this date formatter.



 let dateFormatter = DateFormatter()
dateFormatter.locale = Locale(identifier: "en_US_POSIX")
dateFormatter.dateFormat = "yyyy-MM-dd'T'HH:mm:ss'Z'"
dateFormatter.isLenient = false


If it is not in this format you probably must take into account time zone or daylight saving.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53500780%2fuidatepicker-shows-incorrect-time%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I guess that probably you are using the wrong date formatter to convert the date you are receiving from the server.

    Is the time you receive from the server a string?

    If it is a string, in which time zone is set?

    You must take that into account before parsing it, usually servers returns a en_US_POSIX date string that you can parse with this date formatter.



     let dateFormatter = DateFormatter()
    dateFormatter.locale = Locale(identifier: "en_US_POSIX")
    dateFormatter.dateFormat = "yyyy-MM-dd'T'HH:mm:ss'Z'"
    dateFormatter.isLenient = false


    If it is not in this format you probably must take into account time zone or daylight saving.






    share|improve this answer




























      0














      I guess that probably you are using the wrong date formatter to convert the date you are receiving from the server.

      Is the time you receive from the server a string?

      If it is a string, in which time zone is set?

      You must take that into account before parsing it, usually servers returns a en_US_POSIX date string that you can parse with this date formatter.



       let dateFormatter = DateFormatter()
      dateFormatter.locale = Locale(identifier: "en_US_POSIX")
      dateFormatter.dateFormat = "yyyy-MM-dd'T'HH:mm:ss'Z'"
      dateFormatter.isLenient = false


      If it is not in this format you probably must take into account time zone or daylight saving.






      share|improve this answer


























        0












        0








        0







        I guess that probably you are using the wrong date formatter to convert the date you are receiving from the server.

        Is the time you receive from the server a string?

        If it is a string, in which time zone is set?

        You must take that into account before parsing it, usually servers returns a en_US_POSIX date string that you can parse with this date formatter.



         let dateFormatter = DateFormatter()
        dateFormatter.locale = Locale(identifier: "en_US_POSIX")
        dateFormatter.dateFormat = "yyyy-MM-dd'T'HH:mm:ss'Z'"
        dateFormatter.isLenient = false


        If it is not in this format you probably must take into account time zone or daylight saving.






        share|improve this answer













        I guess that probably you are using the wrong date formatter to convert the date you are receiving from the server.

        Is the time you receive from the server a string?

        If it is a string, in which time zone is set?

        You must take that into account before parsing it, usually servers returns a en_US_POSIX date string that you can parse with this date formatter.



         let dateFormatter = DateFormatter()
        dateFormatter.locale = Locale(identifier: "en_US_POSIX")
        dateFormatter.dateFormat = "yyyy-MM-dd'T'HH:mm:ss'Z'"
        dateFormatter.isLenient = false


        If it is not in this format you probably must take into account time zone or daylight saving.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 27 '18 at 13:46









        AndreaAndrea

        19.8k967106




        19.8k967106
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53500780%2fuidatepicker-shows-incorrect-time%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Lallio

            Unable to find Lightning Node

            Futebolista