Use SFDataForm with an error:"Java.Lang.IllegalArgumentException: Unsupported ISO 3166 country: und"

Hello, my name is Daniel.I try DataForm follow the sample in document ,
but I get the error  
"Java.Lang.IllegalArgumentException: Unsupported ISO 3166 country: und".
Why did this happen?

3 Replies

SV Srinivasan Vasu Syncfusion Team April 18, 2018 01:05 PM UTC

Hi Daniel, 
Thanks for contacting Synfusion support. 
We have checked your query with simple DataForm sample. In the sample, we have changed the CultureInfo for NumericEditor to reproduce the issue. But we could not meet your scenario in our side. The issue may occur due to setting incorrect Localization format (ISO standard) in Xamarin.Forms.  
So, could you please provide below details? 
  • Configuration details (Xamarin version and Android version).
  • Culture info used.
  • Syncfusion version details and Controls used in your application with SfDataForm.
  • Code snippet/ issue reproducing sample along with replication procedure.
It will be helpful for further analysis and provide you better solution. 
Regards, 
Srinivasan 



AL Ali September 22, 2018 11:58 AM UTC

Hi All,

I am receiving the same error on any integer object used in my dataform!!!

Java.Lang.IllegalArgumentException: Unsupported ISO 3166 country: en

I have no clue why this is happening and how to mitigate or resolve it! Can you assist please


JN Jayaleshwari N Syncfusion Team September 24, 2018 11:24 AM UTC

Hi Ali,  
  
Thank you for using Syncfusion Products. 
  
The reported error "Java.Lang.IllegalArgumentException: Unsupported ISO 3166 country: en" occurs when the default Region/Language in the Locale property is not provided and only one value is set.   
  
Please set the values as suggested in the below public forum link .

Linkhttp://stackoverflow.com/questions/15278640/unsupported-iso-3166-country-es  
 
   
Also, the code to detect which language to display must be platform-specific because iOS, Android, and UWP all expose this information in slightly different ways. The platform-specific code must also handle cases where the operating system allows the user to configure a locale identifier that is not supported by .NET's cultureInfo class. In these cases, custom code must be written to detect unsupported locales and substitute the best .NET-compatible locale. Kindly refer the below link for more details.  
  

If you still face issues with the control, please provide us a sample along with replication procedure, such that it will be helpful for us to analyze and provide us a better solution. 
 
 
Regards, 
Jayaleshwari N 


Loader.
Up arrow icon