Data inconsistency between FC and framework's country info causes signup failure.
The issue occurs due to mismatched country data between FC and the framework's built-in country_info.json, causing signup failures in certain regions. The fix likely involves aligning the data sources or handling the discrepancy gracefully. The maintainer has identified the root cause but regional variations may complicate testing.
During signup process, we try prefilling the setup wizard by information user has setup and it is failing in some of the region.
Output of bench version
(paste here)
Data:
{
"data": "FrappeClient Request Failed\n\nTraceback (most recent call last):\n File \"apps/frappe/frappe/app.py\", line 121, in application\n response = frappe.api.handle(request)\n File \"apps/frappe/frappe/api/__init__.py\", line 63, in handle\n data = endpoint(**arguments)\n File \"apps/frappe/frappe/api/v1.py\", line 40, in handle_rpc_call\n return frappe.handler.handle()\n ~~~~~~~~~~~~~~~~~~~~~^^\n File \"apps/frappe/frappe/handler.py\", line 53, in handle\n data = execute_cmd(cmd)\n File \"apps/frappe/frappe/handler.py\", line 86, in execute_cmd\n return frappe.call(method, **frappe.form_dict)\n ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"apps/frappe/frappe/__init__.py\", line 1129, in call\
Claim this issue to let others know you're working on it. You'll earn 10 points when you complete it!