This issue was addressed with Survey123 for ArcGIS version 3.8 (web). If using Survey123 Connect for ArcGIS v3.7, change to the 'Always use the latest version' option in the survey's settings.
The issue is also fixed in the coming Survey123 Connect for ArcGIS 3.9 release.