Hi @equibodyapp,
Please try to implement a condition within the “on change” event to prevent the workflow from running every time you input “a number.” For example:
If this doesn’t resolve the issue, as previously mentioned, we’ll need more details about the problem and your setup to provide more specific assistance. Please share the relevant details, and we’ll do our best to understand the root cause of the issue you’re experiencing and offer appropriate solutions. 
Thank you!
Best regards,
Zeroqode Support Team
Hello @ZeroqodeSupport , How can I use a workflow action to reset the phone number input’s Value to its “Default Value” ?
It seems that the workflow action “Reset a phone number input” actually clears the Value, setting the Value to empty, instead of falling back to the Default Value like any other Bubble input resetting to its “initial content” :
Standard workflow actions like “reset relevant inputs” and “reset a group” are not working and there is no other action available in the plugin to set a value…
Hello @guillaume.raballand,
Thanks for reaching out and bringing this to our attention.
Upon reviewing the information you shared with us, you’re right, with the action “Reset a phone number input” the value from the input will go empty. We have created an improvement task to add an action that will give you the possibility to change the PhoneNumberInput value in the workflow and passed that to our dev team for further consideration. But we can’t give you an exact timeframe when such improvement will take place.
In the meantime, we suggest a temporary solution: incorporating a page refresh into the reset workflow. This step will ensure that the input field reverts to its default value.
Thanks again for your understanding and patience.
Looking forward to your reply.
Best regards,
Zeroqode Support Team
Thank you for your reply and confirmation, unfortunately refreshing the page is not an option because the idea was to reset only the inputs of a specific form by clicking on a “cancel changes” button. Refreshing the whole page would then be an unexpected and bad UX behavior so for the moment I only reset standard inputs and let the phone number inputs with their current value instead of clearing them (even if it’s not the best UX, the chance that users leave a modified but unsaved phone number is quite low). I’ll wait for further updates to manually set a value within the workflow.
Hello @guillaume.raballand,
Thank you for the message.
Indeed, you’ve highlighted a valid point, refreshing the page solution isn’t the best. However, I’m pleased to inform you that our development team has taken note of your concern. We are currently working on an update that will introduce three new actions: “Reset Input,” “Reset All,” and “Set Input Value”. These enhancements are designed to directly address your inquiry and will make it easier to modify the values of the PhoneNumberInput element within workflows.
We’ll make sure to keep you informed with any new information or updates regarding this matter.
Thank you once again for your understanding and patience.
Best regards,
Zeroqode Support Team
1 Like
Hello, I just tested the latest release with the new action to set a specific value to phone number inputs.
It seems to work correctly when the input is visible on the page, but the plugin triggers an error if the input is not visible yet:
It’s not a problem in my use case because I have to use this action only when inputs are already visible, but it may be an issue for other users or situations.
The plugin error triggers a workflow error that prevents further actions in the same workflow from being done.
Hello @guillaume.raballand,
Thank you for your message and observation.
You’re correct, we recently updated the Phone Number Input plugin, introducing new actions and addressing a few minor bugs related to auto-binding.
Regarding your query, you’re also right. The input value can only be modified when it’s visible on the page, otherwise, it triggers an error. I’ll ensure our development team includes this important detail in the documentation.
Thank you again for cooperation and patience.
If you have any more questions or require additional assistance, please don’t hesitate to contact us.
Wishing you an excellent week ahead.
Best regards,
Zeroqode Support Team
Hello, Bubble Community! 
We are thrilled to announce the release of version 1.89.0 for the Phone Number Input + Formatting Plugin. This update brings a slew of enhancements and fixes that make the plugin more robust, user-friendly, and efficient.
Here’s what’s new:
-
Updated Library: We’ve upgraded to the latest version of the phone number input library, ensuring you have access to the most recent features and improvements.
-
Removed jQuery : In our ongoing effort to streamline and modernize, jQuery has been completely removed from the plugin, leading to a lighter and faster performance.
-
Bug Fixes : We’ve squashed several logical bugs that were affecting the functionality of the plugin.
-
Streamlined Settings: The IpInfo Token credential has been removed from the plugin settings for a cleaner setup.
-
Enhanced Field Organization: Fields have now been grouped and reordered to improve usability and your workflow.
-
Extended Documentation: Comprehensive documentation has been added for all fields, making it easier for you to utilize the plugin to its fullest potential.
-
Renamed Fields: To enhance clarity and understanding, some fields have been renamed.
We encourage you to update to the latest version to take advantage of these improvements.
You can find more details and access the updated plugin here.
As always, we’re here to support your journey with Zeroqode. 
Should you have any questions or need further assistance, don’t hesitate to reach out on this forum or contact our support team directly.
Happy Bubbling! 
Best Regards,
Zeroqode Support Team.
Hey @ZeroqodeSupport 
I am testing the plugin and notice a very annoying bug.
If I write a valid number inside the input, select all the text and delete it, the plugin still keep registering the number as valid even with the input empty.
And the PhoneNumberInput’s value will still be the number that was written inside the input before I cleared it.
This type of issue makes impossible to validate the number correctly 
Can you please take a look into it?
Hello @rpetribu ,
Thank you for reaching out to us.
We have tested the concerns you observed and managed to reproduce them on our side. We have already forwarded this to our development team to further investigate and provide a solution in the next plugin version.
Our apologies for any inconvenience this may cause you. If you have any other questions in the meantime, please let us know.
Thank you, and we wish you a great day ahead!
Best regards,
Zeroqode Support Team
@ZeroqodeSupport thanks for this.
Do you have a forecast to solve this issue?
I need this issue fixed in order to finish a important module in my project.
1 Like
Hello @rpetribu,
Thank you for your message.
Our development team is currently looking into the concern you reported to find the best solution and ensure all other functionalities are working well. We are working promptly to have a new plugin version ready as soon as possible. We’ll let you know once it’s available.
Thank you once again. If you have any other questions or difficulties in the meantime, please let us know.
Best regards,
Zeroqode Support Team
1 Like
Hey @ZeroqodeSupport !
It’s been over a week since I reported this bug, which is apparently simple to fix. I have several parts of my app that need to validate the number paused waiting for this update.
I know you guys should be super busy with so many plugins. But I would really appreciate it if you could solve this issue
Thanks
1 Like
Hello @rpetribu ,
Thanks for your message.
We have just updated the PhoneNumber Input plugin to the latest version 1.93.0, where we successfully fixed the states refreshing concerns, ensuring everything runs seamlessly.
Regarding the timing, we have troubleshooted to identify the best solution to address this concern, as the plugin library doesn’t have it by default. Nonetheless, we have fixed it and thoroughly tested it to ensure it won’t affect any other functionalities.
Could you please update the plugin in your app and let us know if it is working well now?
Thanks again, and we look forward to your reply.
Best regards,
Zeroqode Support Team
