Grouped SfRadioButton is not removed from page

[Martin ARION]

Hello Syncfusion support,

I have a problem with SfRadioButton control, which I am struggling with for couple of days already.

I do have an application where Radio buttons are in groups and those groups are generated dynamically based on data.

The problem is, whenever I clear the data and load the new one, it looks like Radio buttons are not disposed from the page.

Please find attached project, with the issue.

The issues seems to be on iOS only. Android application works fine.

Steps to reproduce:

1. Open iOS application

2. Click Clear and new button.

3. Select Q3

4. Click Clear and new button

5. Now you can already see, that Q3 is still selected.

6. Select Q1

7. You can see the result like this:

This is wrong because Q3 shout not be selected.

Strange is that if you click Clear button and New button (instead of Clear and new button), everything works fine. Bud the code in the background is the same.

Important note: Android is not affected with this problem.

Thanks a lot for you help.

Attachment: code_4955e0ab.7z

[Saravanan Madheswaran]

Hi Martin, 

 

Greetings from Syncfusion support.  

 

We have tried the same scenario with the stack layout instead of RadioGroup, the same issue has been reproduced with it. So, we need two business days to validate further, and update you the status on or before 18th May 2021.  

 

Regards, 

Saravanan.   

[Martin ARION]

Hello support,

do you have any feedback about the issue?

Thank you

[Gayathri Manickam]

Hi Martin, 

 

We have validated your query “Whenever clear the data and load the new one, the Radio Buttons are disposed from the page” issue is resolved by Setting CachingStrategy to RecycleElement in the Listview as per the below code snippet and also attached the modified sample for your reference. 

 

Code snippet[Xaml] : 

      <ListView x:Name="listView" CachingStrategy="RecycleElement" ItemsSource="{Binding Questions}" HasUnevenRows="True" SelectionMode="None"> 

        <ListView.ItemTemplate> 

                             <DataTemplate> 

 

                             </DataTemplate> 

               </ListView.ItemTemplate>                                      

      </ListView> 

 

Modified Sample : https://www.syncfusion.com/downloads/support/forum/165426/ze/RadioTest863482571.zip 

 

Please let us know if you have any other queries. 

 

Thanks, 

Gayathri M. 

[Martin ARION]

Hello,

I am not sure this is the solution.

I tried modified solution and upon pressing New button a radio button group appears, but from then I am not able to click on RadioButton neither on other buttons - screen is frozen.

Tested on iOS physical device with latest iOS update.

Thank you

 

[Saravanan Madheswaran]

Hi Martin,  

 

Thanks for the update, we also try to reproduce the same and update you the possible solution in two business days (26th May 2021). And we appreciate your patience until then.  

 

Regards, 

Saravanan.  

[Saravanan Madheswaran]

Hi Martin, 

 

We try to reproduce the reported freeze issue at iphone 7 & 11 simulator at iOS 13.1.2. hence, we do not have physical device availability. And the same item not clear issue noticed with Xamarin.Forms stacklayout. So, we need two more business days (28th May 2021) to validate further. We appreciate your patience until then. 

 

Regards, 

Saravanan. 

[Gayathri Manickam]

Hi Martin, 

 

We have tested the reported problem “After trying modified solution upon pressing new button a radio button group appears, unable to click radioButton neither on other button the screen is frozen” on iOS physical device with latest iOS update and it was working fine at our end. 

 

Could you please share the OS version and device details? It will be helpful for us to provide you better solution at the earliest.  

               

Tested Version : 

 

iPhone OS version	14.6
Syncfusion.Xamarin.Buttons	19.1.0.64
Xamarin Forms	5.0.0.2012

 

Output : https://www.syncfusion.com/downloads/support/forum/165426/ze/Radiobutton-1490389025.zip 

 

Thanks, 

Gayathri M.