This is not yet seems to be solved and its a breaking bug, to avoid this lot of regex and pattern changes are to be needed
Was an official bug report submitted?
Workarounds can be a helpful stopgap measure in some situations, but if a bug report is not submitted, chances are slim the issue will get resolved.
Not submitted, Submitting the bug report looks complex and no list of previous bugs…
I did submit a bug request. I was informed it was an iOS 13 issue, which is accurate. Microsoft PowerApp users are also experiencing the same issue on iOS devices. The workaround of converting the inputs to ‘text’ doesn’t work for me, due to having to run calculations on the inputs which requires it to be a number field.
Hopefully Apple can resolve this issue soon!
1 Like
Cool, thanks for the info, @swvann. The current version of iOS as of this writing is 13.1.3, so maybe it’s fixed in that release? Anyway, thanks for reporting it.
@eve, any chance Bubble will consider making an issue tracker available? It’s precisely this kind of situation where it would be extremely helpful. Just think of the wasted time and network traffic that could have been avoided here if a list of known issues with status, comments, and work-arounds was accessible to Bubble users. 
This topic was automatically closed after 14 days. New replies are no longer allowed.