eTicket 2010 bug notice

[eticketapp]

NOTICE: 1/1/2010 - We have been alerted to a major bug in eTicket that activated today, the first day of 2010. Our date 'picker' inside the app did not handle the year change and does not function correctly. The app will not display any date entry options now and will crash when you try and enter a date in the Itinerary or DVC Calculator.

We are disappointed beyond words by this news and are working feverishly with the programming team and Apple to quickly update the app. We have removed the app from sale on the iTunes App Store until this bug is fixed.

We understand and appreciate your frustration and ask that you have patience while we address this problem and make sure it doesn't happen again.

A temporary work-around is to go into your iPhone Settings>General>Date & Time> Turn off "Set Automatically" and any date in 2009. You can then return to eTicket and enter the dates you want. Go back to Date & Time and turn back on Set Automatically.


-Josh
eTicket Producer

 

[OKW Lover]

Thanks for the note Josh and we appreciate your hard work on fixing this quickly. I guess that's something that the beta testers missed.

 

[eticketapp]

Thanks for the note Josh and we appreciate your hard work on fixing this quickly. I guess that's something that the beta testers missed.

Something I missed to test and something the programming team shouldn't even have had an issue with in the first place. There is nothing we can we do until Monday anyway when Apple opens again.

But I do have to say that the community here on the DIS has been very supportive all throughout this massive project. I mean I'm thinking we're ready to move into a new phase on Monday, you know, start building new features, and instead I find myself with having to pull the app from the store and preparing for the inevitable feedback.

Hey, if this were easy everybody would be doing it!

 

[Cyrano]

Thanks for the update Josh.

 

[OKW Lover]

Something I missed to test and something the programming team shouldn't even have had an issue with in the first place. There is nothing we can we do until Monday anyway when Apple opens again.

But I do have to say that the community here on the DIS has been very supportive all throughout this massive project. I mean I'm thinking we're ready to move into a new phase on Monday, you know, start building new features, and instead I find myself with having to pull the app from the store and preparing for the inevitable feedback.

Hey, if this were easy everybody would be doing it!

Yeah, I understood that Josh. My original post was definitely tounge-in-cheek.

We appreciate the work you put into the app. Any hints about what's next?

 

[yitbos96bb]

Something I missed to test and something the programming team shouldn't even have had an issue with in the first place. There is nothing we can we do until Monday anyway when Apple opens again.

But I do have to say that the community here on the DIS has been very supportive all throughout this massive project. I mean I'm thinking we're ready to move into a new phase on Monday, you know, start building new features, and instead I find myself with having to pull the app from the store and preparing for the inevitable feedback.

Hey, if this were easy everybody would be doing it!

Based on the number of apps, it feels like everyone is... but there is a big difference between doing it and doing well and right. You are doing it well and right. Keep up the good work.

 

[katscradle]

Thank you for letting me know, I have been trying to use my DVC calculator for 2 weeks for next year. It would not let me enter a date for 2010, but I just thought I was doing something wrong.
Anyway thanks again and I will wait patiently.

 

[eticketapp]

Kats- the problem is definately on our end. We'll get the fix out ASAP.

And as for what is going to be coming next...I don't want to say juusssst yet becuase it's hard to say how long it will take to build and test. I've certainly heard the feedback and am going to focus on buildIng up the itinerary.

 

[k5jm]

Kats- the problem is definately on our end. We'll get the fix out ASAP.

And as for what is going to be coming next...I don't want to say juusssst yet becuase it's hard to say how long it will take to build and test. I've certainly heard the feedback and am going to focus on buildIng up the itinerary.

Josh had a Y2K+10 bug. 10 years, hmmm, better late than never.

 

[katscradle]

Kats- the problem is definately on our end. We'll get the fix out ASAP.

And as for what is going to be coming next...I don't want to say juusssst yet becuase it's hard to say how long it will take to build and test. I've certainly heard the feedback and am going to focus on buildIng up the itinerary.

Thank you, your a sweetheart!