My client is using the No Code Monkey Multi Input Validator, but in Android build, it is giving an error
.She was ready to go live, but this is her road block.
We tried the switch below in both on and off positions, but no luck in removing the error.
She also tried to report the bug but is unable to log into NocodeMonkey.io - it keeps giving her an error if she tries to reset her password.
@NoCodeMonkey can you help?
Thank you in advance.
Hi @Gaby,
I’m very sorry for the situation! NoCode Monkey is still there and available!
And yes, the multi-input validator component had issues with new react native upgrades but fixes has been pushed and they are in-progress for the approval to be live. Fixes should be available in the component soon! I’ve pinged Matthew (the CEO) and he will post a message here.
Also, to contact the NoCode Monkey support team, just use the ‘Contact Us’ page in the website and no need to log in.
Thank you and have a great day!
Ok, do you have an estimated date for availability? My client is eager to get a date she can go live - I dont want to tell her “soon”.
Hey Gaby, thanks for pinging us about this. I double checked and pushed the latest version to Adalo. I’ll ping them to make sure it’s on their priority list. They normally turn these around pretty quickly, usually within a couple of days!
You can always reach out to me at matt@nocodemonkey.io or to our support team at support@nocodemonkey.io if you have any questions.
Hey @Gaby, they let me know the new version is live now! We tested it a bunch and it should be solid.
Let me know if there’s any issues with that version and we can get it fixed quickly for you.
Thanks!
Matt
Hey Matt, that is good news! So does that mean we need to delete the old version and do all the settings again using the new version? Trying to gauge the amt of work ahead!
Most of the time the component should update when you refresh the page or after the update is live. Sometimes we have seen the component not getting the update so you would need to delete the component, re add it, and update the settings before publishing a new build for the update to hit the component properly.
Let me know how it goes so I know how it went!
The component says it was updated 3 years ago. If it was recently updated, should this not have a more recent date? Also I dont see a way to remove and redownload. But first please confirm this is in fact an updated version.
You would remove it in the app editor and re-add it there to get everything to work. It’s just that the updates sometimes don’t get pushed to components that are already in the editor. That’s when you would follow the steps I mentioned.
We’ve seen this on other components that we’ve updated. People confirmed the new version works but the page says the most recent update was months or years ago. I believe it’s on the Adalo side as I have no way of editing that field. I’m working with Adalo to get that fixed so you can be assured there is a new version there!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
