As per title, the implementation of sayText() on mobile devices is slightly broken.
Multiple sayText() are supposed to queue the text, desktop browsers behave exactly as written on the documentation, mobile devices struggle to queue the lines in the correct order.
To reproduce the bug:
1. Navigate on API example with a mobile device: http://www.oddcast.com/support1/tts_limit.html
2. Click "sing a song"
The 5 TTS strings should be played back in order.
TTS comes in on a random order, sometimes with overlapping audios, sometimes breaks after 2 times it gets played.
Chrome / Android 9
Chrome / Android 10
Customer support service by UserEcho