After local sync: wrong start date for a repeated scheduled monthly action

1.11.15 desktop server, 1.10.0 Android client

Scheduled repeated action correctly shows in “Scheduled” list on desktop as “Next Week” action (Jul 6 start date). When locally synced to Android phone, same action shows as “Future Dates” action (Dec 7 start date). Action scheduling settings are: Start date Jul 1 / repeats monthly / every 6 months / on 1st Monday, so start is on Jul 1, but because it’s not a 1st Monday it postpones it to Jul 6 as expected. Selecting the action on Android shows Jul 1 start date correctly. Also “1st Monday” is still correct (Dec 7 is Monday), but date is wrong

Same problem with other 2 similar actions with similar settings (they repeat every 3 or 4 months). Yearly repeating actions do not have this problem and sync correctly.

Date settings and internet connection are properly operating on both devices. Clean pull does not fix it. Pushing from Android client into desktop server still shows correct date on desktop

Did more testing: same thing when choosing another day of the week with same settings as described above. But it works as expected when I choose “on 1st Day”, which is what I actually needed (but it wasn’t selected by default, which I think it should’ve been as the most expected scenario)

Hi, can you please provide these details for one of the scheduled tasks.

  1. Complete scheduling settings that you used when you originally created the action?
  2. After sync, when you view the scheduling settings, are they the same between the two devices?
  3. What unexpected behavior are you observing on each of the devices?

This would help me understand the issue. Thanks!

  1. Yes

  2. Android: action is placed in “Future Dates” instead of “Next Week”. Android: action has “Dec 7” start date label instead of “Jul 6”.

P.S.: creating same action on android instead of desktop has identical effect on both devices (correct on desktop, wrong on android)