Is that still the case, as another patch has been uploaded earlier today to address this?
This was tested on an Android app at time of release.
Some detail about this issue :
The cause of this issue was a recent change to our legacy API, resulting in the default values being used when the time controls values are not available, as you discovered. The update should work around this.
edit : It was unfortunate that this problem resurfaced again on the phase 2 update (Thread 193177
) - my initial response to this thread predated that work.