- Home
- Forum
- Xamarin.Forms
- SfPdfViewer.ClearAllAnnotations is broke
SfPdfViewer.ClearAllAnnotations is broke
ClearAllAnnotations() does not clear Stamp annotations on iOS.
ClearAllAnnotations() does not clear ANY annotations on UWP.
ClearAllAnnotations() appears to work fine on Android.
1. See attached example (latest Xamarin.Forms, Syncfusion 18.1.0.57)
2. Select Stamp button to add a stamp annotation
3. Select Clear to clear all annotations
Result iOS => stamp annotation is not removed, but others are.
Result UWP => no annotations are removed
Regards,
Arthur
Attachment: GettingStarted_6e960be4.zip
SIGN IN To post a reply.
3 Replies
1 reply marked as answer
AV
Ashokkumar Viswanathan
Syncfusion Team
June 18, 2020 09:10 AM UTC
Hi Arthur,
Thank you for contacting Syncfusion support.
We were able to reproduce the issue, “Annotation are not cleared properly while using ClearAllAnnotation API”. Currently, we are validating the issue and we will update further details on June 22nd , 2020.
Regards,
Ashok Kumar Viswanathan.
AV
Ashokkumar Viswanathan
Syncfusion Team
June 22, 2020 01:15 PM UTC
Hi Arthur,
We have confirmed that the issue “Annotation are not cleared properly while using ClearAllAnnotation API” is a defect and logged a defect report for this issue. The patch for this issue will be delivered on July 13th , 2020.
Please find the feedback link,
Regards,
Ashok Kumar Viswanathan.
AV
Ashokkumar Viswanathan
Syncfusion Team
July 13, 2020 03:42 PM UTC
Hi Arthur,
We have resolved the issue, “Annotation are not cleared properly while using ClearAllAnnotation API“ and custom NuGet for the same can be downloaded from the following link
Custom NuGet :
Please find the feedback link,
Disclaimer:
Please note that we have created this NuGet for version 18.1.0.59 specifically to resolve the following issue(s) reported in this/the forum. 155272
Please note that we have created this NuGet for version 18.1.0.59 specifically to resolve the following issue(s) reported in this/the forum. 155272
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 2020 Volume 2 service pack release which will be expected to be available in the month of July 2020.
Regards,
Ashok Kumar Viswanathan.
Marked as answer
SIGN IN To post a reply.
- 3 Replies
- 2 Participants
- Marked answer
-
AB Arthur Butler
- Jun 17, 2020 01:48 PM UTC
- Jul 13, 2020 03:42 PM UTC