PdfViewer Changes Culture on Android/iOS

Hi, 
we have a Xamarin Contentpage, wich is Programmicaly built (Not Xaml).
When we use the PdfViewer the Culture of everything changes. 
Datepickers and other things like DateTime.ToString("d") change from "de" (wich is our Culture) to something Called Invariant Language(Invariant Country).

This only happens after we Initialize a PdfViewer.

We have a workaround wich only works on iOS:

CultureInfo _currentCulture;

public void InitPdfViewer() 
{
     _currentCulture = Thread.CurrentThread.CurrentCulture;
     _internalPdfViewer = new SfPdfViewer()
}
//Called when leaving Content Page
public void unloadViewer()
{
     _internalPdfViewer.Unload();
     Thread.CurrentThread.CurrentCulture = _currentCulture;
     Thread.CurrentThread.CurrentUICulture = _currentCulture;
}


We are using Version 18.3.0.35 and have tested this Bug on Android 9 Emulator  x86 and a physical iPad Air 2.

Why is the Culture Changing and how can we reliably fix it?


12 Replies 1 reply marked as answer

AV Ashokkumar Viswanathan Syncfusion Team October 7, 2020 10:59 AM UTC

Hi Patrick, 
 
Greetings from Syncfusion support, 
 
We have tried to replicate the issue, “Culture changes while using SfPdfViewer control” in our end, its working as expected.  
 
Please find the sample which we have tried in our end, 
 
Kindly share the following details to analyze more on this issue and assist you with the better solution.      
  1. Simple sample/ modify the above sample(if any changes)
  2. Xamarin Forms version.
  3. SfPdfViewer version.
  4. Platform
  5. Complete device specification.
  6. Replication procedure/video illustrating the issue in detail.
 
Note : We have used German language to reproduce the issue. 
 
Regards, 
Ashok Kumar Viswanathan. 



PK Patrick Kehr October 7, 2020 12:04 PM UTC

Thank you for the Quick Reply.
1. Updated Code to follow my Workflow.
2. Xamarin Forms Version: Our Project is 4.6.0.1180, your Testproject was 4.8.0.1269
3. PdfViewer Version: Our Project is 18.3.0.35
4. Built on Windows Bug found On Android and iOS (we dont build UWP)
5. Added Image of Emulator Settings.
6. Added Video of the bug happening.

The mentioned Code, Video and Image is attached as a Zip File.


Attachment: CultureSampleChanged_7d2d2be7.zip


AV Ashokkumar Viswanathan Syncfusion Team October 8, 2020 06:42 AM UTC

Hi Patrick,   
   
Thank you for providing the requested details, 
   
We were able to reproduce the issue, “Culture changes while using SfPdfViewer control” in our end.  Currently, we are validating the issue and  we will update further details on October 12th , 2020.  
  
Regards,  
Ashok Kumar Viswanathan. 



SP Satheesh Palanisamy Syncfusion Team October 12, 2020 06:14 PM UTC

Hi Patrick,

We are still validating the issue “Culture changes while using SfPdfViewer control” this with high priority and we will update the further details on October 14th,2020.

Regards,
Satheesh Palanisamy.




AV Ashokkumar Viswanathan Syncfusion Team October 14, 2020 02:21 PM UTC

Hi Patrick, 
  
We have confirmed that the issue “Application language culture changes while using SfPdfViewer in Xamarin.Forms” is a defect and logged a defect report for this issue. The patch for this issue will be delivered on November 4th , 2020. 
 
Please find the feedback link below, 
  
Regards 
Ashok Kumar Viswanathan. 



AV Ashokkumar Viswanathan Syncfusion Team November 4, 2020 12:37 PM UTC

Hi Patrick, 
 
The issue "Application language culture changes while using SfPdfViewer in Xamarin.Forms" has been resolved in our weekly NuGet release (v18.3.0.42). Kindly update to the mentioned version to get the issue resolved. 
 
Please find the packages link below, 
 
Regards, 
Ashok Kumar Viswanathan. 



UN Unknown January 11, 2021 07:41 AM UTC

Hello,

this issue still occurs for me with:

SfPdfViewer 18.4.0.33
Xamarin.Forms 5.0.0.1874

Best regards,
Florian


MK Muralitharan Karikalan Syncfusion Team January 12, 2021 06:07 PM UTC

Hi Florian, 
 
Sorry for the inconvenience caused, 
 
We were able to reproduce the issue, Application language culture changes while using SfPdfViewer in Xamarin.Forms . Currently we are working on this as high priority. We will update the further details on January 15th ,2021. 
 
Regards, 
Muralitharan K 



MK Muralitharan Karikalan Syncfusion Team January 15, 2021 05:31 PM UTC

  
Hi Florian,

 
Sorry for the inconvenience caused, 

We are still validating the issue “Culture changes while using SfPdfViewer control” this with high priority and we will update the further details on  January 19, 2021 without any further delay.

Regards,
 
Muralitharan K. 



MK Muralitharan Karikalan Syncfusion Team January 19, 2021 06:56 PM UTC

Hi Florian, 
  
Sorry for the inconvenience caused, 
  
We are still validating the issue “Culture changes while using SfPdfViewer control” because of the issue occurs from the combination of Syncfusion SfPdfviewer and PDF . We are working on this as high priority and we will update the further details on January 21st , 2021  without any further delay. 
  
Regards, 
Muralitharan K 



MK Muralitharan Karikalan Syncfusion Team January 21, 2021 03:01 PM UTC

Hi Florian, 
 
Thank you for your patience. 
 
We have  confirmed the issue, “ Culture changes while using SfPdfViewer control” as bug . We will resolve and provide the patch for the issue on January 27th ,2021. 
 
Regards, 
Muralitharan K 



MK Muralitharan Karikalan Syncfusion Team January 27, 2021 06:15 PM UTC

Hi Florian, 
 
Thank you for your patience,     
    
We have resolved the issue, Culture changes while using SfPdfViewer control and the custom NuGet for the same can be downloaded from the following link            
         
Custom NuGet :     
    
Disclaimer:   
Please note that we have created this NuGet for version 18.4.0.34 specifically to resolve the following issue(s) reported in this/the Forum 158450. 
 
 
 
Note: Please install the NuGet in the following order  
1. Syncfusion.Xamarin.PDF [Patched NuGet from the above]  
2. Syncfusion.Xamarin.SfPdfViewer [ From Nuget.org]  
 
Note : Kindly follow the steps to clear the NuGet cache and then install patched NuGet to get the issue resolved.       
           
This fix will be included in our 2021 Volume 1 main release which is expected to available in the month of March 2021.        
     
Regards,     
Muralitharan K.   


Marked as answer
Loader.
Up arrow icon