Validation inconsistent on Mobile Devices

[jasonatvelocity]

Make sure that you are familiar with documentation before submitting an issue.

https://vuelidate-next.netlify.com/

Describe the bug
We have a date picker that populates an "issueDate" text box field in the following format: "MM/YYYY". Vuelidate works great on all devices except mobile. We've mostly been able to reproduce on the iPhone devices using BrowserStack or a mobile phone.

In particular iPhone 15 v17.3, but it intermittently fails on all of them (sometimes it works, sometimes it doesn't). The problem is that when the date value is picked using the date picker the value is correctly set on all the models (inside v$ too) but the "this.v$.model.issueDate.required.$invalid" returns true (evaluates incorrectly).

To make matters worse, this issue is intermittent and very hard to reproduce (happens about half the time). Important note - it has only started happening since we upgraded to Vue 2.7. Prior to our upgrade it was not an issue.

We've inspected the v$ object and everywhere show's our date being set, however the $invalid flag is erroneously evaluated as true. Short of rolling our own validation on this field we are currently at a loss for how to fix it. Upgrading to the latest version of Vue is not yet an option for us. We've tried dozens of different approaches after reviewing the vuelidate documentation all met with no success.

To Reproduce
Steps to reproduce the behavior:

1. Create a text box field with a date picker (we used the vuetify v-text-field and v-date-picker).
2. Using a mobile device, attempt to pick a date (happens in all browsers, but we've been using safari to test)

Expected behavior
Vuelidate evaluates as valid when it is valid.

Screenshots

[jasonatvelocity]

Just to follow up, we removed the required validator in the validations section of code and implemented custom checking to see if the property is set. While this fixes our problem there appears to be a deeper issue with the required decorator. Only way we were able to solve the issue was to circumvent vuelidate altogether. Hope this helps others facing similar issues. From what I’ve seen there appears to be severe issues around vue 2.7 and vuelidate making it difficult to use.

[jasonatvelocity]

To the vuelidate team: please reach out and I can show the issue first hand. Unfortunately our code is proprietary so unable to share on this forum specific code samples.