Nativescript-ui-feedback: DataForm's validation wont work on iOS after bringing app from background

[trodellez]

We are having this issue with Dataform on iOS when the component is put in background and then brought back to foreground, none of Dataform events such as propertyValidate or propertyValidated would be fired and executing validateAll() wont return any value.
This happens only on iOS and I have made a simple playground project to clarify it better

https://play.nativescript.org/?template=play-ng&id=hqZMRm&v=62

• **Progress NativeScript UI plugin version: 6.0.0
• **CLI: 6.4.1
• **Cross-platform modules: 6.5.1

Please tell us how to recreate the issue in as much detail as possible.

1. Start the application on iOS
2. type some charachter in firstname field ( on the console validation events would be logged )
3. press home ( put app in background)
4. click again on app icon ( bring it back to foreground)
5. start typing in other fields or click continue

none of the validations would pass and on the console it can be seen that none of the events are being called.
I would appreciate any help regarding this since it is a critical issue.

[alexander-mai]

I have the same problem.
Whill this be fixed anytime?

[sandwai-scottjackman]

Same problem here with the exact same versions. This is really affecting our app - can someone please look into this asap?

[sandwai-scottjackman]

After a frustrating 3 hours trying to find a workaround for this...... I did! This solution may not be appropriate for everyone, but it works for me.

Make sure that the form is opened in a modal. That's it! The validation events continue to fire normally after the app has been resumed from background.

I'm using the vuejs flavour of NS so this is very easy to do - I can just choose to open the component in a modal for iOS, and navigate to it normally for Android (as android has it's own specific issues with modal content and raddataform).

This is still a very bad bug, as it really makes normal use of forms extremely unusable for most applications, but this workaround does exist. No idea why :(

Hope this helps someone.

[alexander-mai]

Does nobody else has this problem or nobody else using the RadDataform.
I switched to use ReactiveForm for Angular Flavor. There isn't this bug and the material layout is also used on iOS instead of the splitted view.

[sandwai-scottjackman]

Does nobody else has this problem or nobody else using the RadDataform.
I switched to use ReactiveForm for Angular Flavor. There isn't this bug and the material layout is also used on iOS instead of the splitted view.

RadDataForm is a horrible buggy beast. It promises a lot, but under-delivers on nearly everything. There are so many bugs and quirks - usually completely different for iOS and Android, so there is rarely a on-fits-all solution, and often you'll need to have completely separate components for each os.

The app I've developed makes extensive use of RadDataForm, but there are so many workarounds to deal with all of the above that it's blown out our production by about 6 months. No joke.

Happy to share my knowledge with anyone who is experiencing these issues. Hopefully RadDataForm gets a huge overhaul / rewrite soon, but I wouldn't hold my breath on that one. :(