Disney World app "My Plans" broken

[LD500]

The Disney World app on my iPhone was working fine until about 2 days ago when the "My Plans" section started incorrectly listing items under "Tomorrow". We're not going to Disney World until next year.
Also all the subsequent days seem to be shifted down. Example: Mar 15 items are under Mar 14 heading.

Example of what was under "Tomorrow", it lists us checking into our first resort and going to Chef Mickey's under "Tomorrow". When you click on those items, it lists their correct dates far in the future.

It might have coincided with Apple's latest iPhone iOS update.
I'm quite sure everything should be fine as it looks perfect when I log into the My Disney Experience website but it's sure not right on the iOS App.

Anyone else experiencing this?

Thank You

 

[erionm]

Everything shows correctly for me. I'm using MDX on an iPhone 6 Plus running iOS 9.1.

 

[erionm]

A new update to MDX is available (v3.1.1). You might want to update yours and see if that helps. If it doesn't, try uninstalling and then reinstall MDX to see if that fixes your issue.

 

[Hibiscus]

I checked my app for your issue & everything looks fine.

 

[Madame]

Mine are showing like this as well. The actual date for my plans is off by one day. So the plans for Dec 20th are listed, for example, and the date Dec 20th is listed at the bottom of the plans for that date.

Almost gave me a heart attack 2 days ago. I thought I'd accidentally scheduled everything one day off!

 

[LD500]

"Heart attack" being one day off Madame? I thought I accidentally booked my first resort stay to start tomorrow when it should have been 4 months later.

Just updated to the latest iOS Disney World app right now, deleted the app, then reinstalled it. Same problem.

 

[LD500]

All the reservation dates on my app are now correct again. Who knows why but it's fixed, probably because "Tomorrow" passed.

 

[GreatLakes]

On the rare occasion something wasn't showing correctly in my MDE app clearing the cache and force stopping it always fixed it for me. Of course if it is a server side issue this would only fix an issue related to the session.