Hey @thethinklab.au ,
Nice work sorting this out! Thanks for sharing , ‘Value without country code’ being the key is a great catch, and We agree the label could be clearer. Those screenshots really help clarify it for others (Aus and US examples are spot on). Appreciate the update.
Regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hey @ZeroqodeSupport !
Some of my users start reporting issues with the plugin.
I will share some images.
The problem is happening regardless of the browser.
It is happening on iPhone (Safari), Chrome and Firefox.
And to make matters worse, not all users are experiencing this problem. For example, I can’t simulate the error on my computer, because everything works fine for me. But every day, more and more users are reporting this same problem.
Could you take a time to taka a look into it?
Hi @rpetribu,
Thanks for getting in touch. We’ve reviewed your issue with our dev team. From your screenshots, the problem could be due to the behavior of the plugin in certain devices or browsers.
We’ve tested the plugin demo page and everything works as expected on mobile devices, including iPhone, Chrome, and Firefox browsers.
Here are a few things we suggest to further investigate the issue:
Plugin Version: Please ensure you’re using the latest version of the plugin. We released an update that fixed the placeholder, so updating to the latest version might resolve the issue.
Browser and OS: Could you share more information about the OS and browser versions your users are using when experiencing the issue? It would be helpful to know whether it’s a specific browser or OS causing the problem.
Mobile or Web App?: Are you testing the plugin on a web app or a native app? All our plugins are designed for Web Apps first.
Element Configuration: Could you provide more details about how you’ve set up the Phone Number Input element and the workflows associated with it? We recommend reviewing your element configuration and ensuring that the input field is correctly bound to the right format (e.g., for international numbers or specific formats).
Test on Demo Page: To check whether this is an isolated issue, please test our live demo page on your mobile device and see if the issue persists. If the demo works fine, it might indicate that there’s an issue with the setup in your app.
Once we have more information, we can better assist you in resolving the issue. Please let us know if these steps help, or if you need further clarification.
Looking forward to hearing back from you!
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hey @ZeroqodeSupport 
We are in the last version. Finally the error started appearing for me too, so I can share the console log with you.
Nothing was done in the App.
Not a single deploy in last month.
Thanks!
Hello @rpetribu,
Thank you for your reply.
It appears you have encountered a “Recursion/Circular reference” error. This issue occurs when the plugin uses internal variables for its fields( referencing PhoneNumberInput in the conditionals directly), which can lead Bubble to erroneously flag it as cyclic.
To resolve this issue, please refer to this documentation: https://docs.zeroqode.com/plugins/phone-number-input-formatting - and scroll down to the “Workflow example” section. There, you can learn more about the error and how to fix it.
Could you please follow the instructions and try using a state instead of referencing the element directly? Let us know how it works for you.
Thank you again, and we look forward to your reply.
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Sorry for the late response. Unfortunatelly this is not the case.
We don’t have any mention to the input in any condition or dynamic field inside itself.
I kept downgrading until I reached the version 1.87.0. Now it works.
If I upgrade to 1.88.0 it will stop working.
One thing that I noticed was that, even with the version 1.87.0, I see the same error in console, but the plugin works perfectly:
Hi @rpetribu,
Thank you for getting back to us.
As mentioned in our previous message, the error might be caused by a conditional applied directly on the Phone Number Input element—specifically, the AAN property, which refers to the Border Color. We had a similar case before that was resolved; you can check the related forum thread here:
https://forum.zeroqode.com/t/phone-number-default-value-error/11550/3
Example of Conditional:
Please review the Conditional tab of your Phone Number Input element and the conditions you’ve set there. Both errors are caused by referencing the element’s own state in its conditional tab, which creates a recursion/circular reference.
To fix the “Recursion/Circular reference” error, please see this section in our documentation: Phone Number Input + Formatting (scroll down to “Workflow example”). It explains the issue and provides a solution.
If you need further assistance, feel free to share screenshots of your element’s configuration, a link to your app, steps to reproduce the issue, and a test account for us to check.
Thank you, and we look forward to your reply.
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi @ZeroqodeSupport !
Thanks again, as always, for the quick reply.
I did indeed have conditional formatting applied to the input, which changed the border color when I hovered over the element.
But even after removing this conditional formatting, the error persisted. So I started trying to figure out the mystery, since when I inserted a new element into the editor, this new element loaded normally, EVEN with the conditional formatting applied to it as well.
So I started inserting into this new element, item by item, the same settings that I had in the element that was presenting the problem. I finally managed to figure out the problem and as you can see below, I was able to get one of the inputs to load normally again, containing exactly the layout I wanted and without giving up the conditional formatting.
The problem is with the “Auto Country Detection” option. The configuration for both is exactly the same. The only difference between them is that the input that is working has this option unchecked. The input that is NOT working has this option checked.
I also visited the plugin page, where I was able to validate my theory.
And in the editor:
As you reported that for you, there were no problems. I decided to reload the page with my VPN turned on…
There is probably an issue with the plugin loading for users from Brazil if the option to automatically detect the country is enabled. All my users are from Brazil and everyone we have approached is having this problem.
So, for now, I disabled this option from all my inputs…
But I think it’s worth investigating…
Hi @rpetribu,
Thank you so much for your detailed reply. 
I’ve passed this information on to the dev team, and they will investigate whether there is a plugin restriction or limitation due to the library used, and if there’s a possible workaround for this.
Could you also confirm if the “Auto Country Detection” option is what causes the recurring issue in the console, or if it’s related to the conditional for the border color?
We will get back to you as soon as we have any updates, thank you for your understanding and cooperation. 
Wishing you a great start to the week! 
Regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hey @ZeroqodeSupport !
No, it is related to the border color. The error keeps appearing for me in the console, but it doesn’t impact the plugin’s operation at all.
Hi @rpetribu,
Thank you for your response and cooperation throughout this process.
We’ve updated the Phone Number Input + Formatting plugin to Version 1.99, which includes a fix for the “Auto Country Detection” feature.
Please update the plugin in your app to the latest version and let us know if this resolves the issue with detecting Brazilian phone numbers.
Wishing you a great weekend ahead.
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi @rpetribu,
Could you please confirm if you’ve seen our previous message on the forum regarding the plugin update?
Have you had a chance to test the latest version? Is everything working as expected now?
We look forward to your reply. 
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi @ZeroqodeSupport ! Sorry, I miss your last message!
Yesssss, it is now working again 
Thanks once more.
Hi @rpetribu,
Thank you for your confirmation.
We’re delighted to hear that everything is now working well. Please don’t hesitate to reach out if you need further help or assistance – we’re always happy to support you.
If you’re enjoying our plugin, we’d be so grateful if you could take a moment to rate it! You can head to the Plugins tab in the Bubble editor, search for the plugin by name, and leave the stars you think it deserves. Your feedback truly motivates us to keep improving. 
Have a great weekend ahead.
Regards,
Support Team
Browse all Zeroqode Plugins for Bubble
I just paid 60$ for a plugin that pretty much sucks.
The country code dropdown is unusable.
(if you can see, it goes behind other inputs).
I tried to ‘bring it to front’ but in responsive in a popup, not working.
Very disapointing.
Hi @tart2000design ,
Thanks for reaching out and for sharing the screenshots!
We’re sorry for the frustration this has caused. We did double-check our demo page here: Phone Number Input Demo and the country code dropdown appears to be working as expected.
To help us investigate why it’s behaving differently in your setup, could you please confirm:
Based on what you’re describing, it might be related to a browser-specific tooltip or a Z-index conflict, but we’ll need these details to confirm and provide guidance.
Thanks for your patience, and we’ll do our best to get this sorted!
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
I’m using it in a RE / Popup.
It disappears behind other inputs as you can see.
I’m using the latest version on Chrome.
Hi @tart2000design ,
Thanks for getting back to us and for confirming those details!
We’ve double-checked the dropdown behavior inside a popup (including within reusable elements) across multiple test setups, and everything appears to be displaying correctly on our side.
At this point, we’d like to confirm the exact plugin version you’re using, sometimes subtle differences between versions can cause rendering inconsistencies.
Also, if possible, could you please share a short video showing the issue in action? That would help us clearly see what’s happening and replicate your setup more accurately to identify the root cause and provide a proper fix.
Looking forward to your reply!
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
