Does the same issue occur with a new application that only contains a TMSFMXWebOSMaps component?
We are investigating this issue and will report back as soon as possible.
We have been able to reproduce this issue.
However due to the current high workload caused by other ongoing projects we haven't been able to apply a fix at this time.
As soon as we have been able to allocate sufficient development we'll continue searching for a fix.
Unfortunately there hasn't been any progress on this issue.
We have determined that the version of the OpenLayers API which the TMS WebOSMaps is currently based on is no longer working as expected in combination with recent mobile browsers on both Android and iOS.