Impossible to zoom out in certain occasions

95% of the cases the zoom on the pdfviewctrl works fine.

We've experienced a rather odd bug and can't find out what causes it and if it's our fault or not.

The bug:
When the bug occurs this is what happens:

- The controller opens the document and displays it properly.
- The when you zoom in to -let's say- 1.5 zoom factor it shows the zoom properly.
- When we want to zoom out, it seems to be zooming as we keep the pinch going but afterwards it resets to 1.5
- When we want to zoom in further, there seems to be no problem.
- So, we zoom in a little more and the zoom appears to be 2.5.
- After we try to zoom it out the zoom factor jumps to 1.5 again (the number it seems to be stuck on.)

-Now , if we close the document and open another (same instance of the viewcontroller), it seems to not follow our instruction to fit to the width of the superview but it sets the zoom to -guess what- 1.5

It's a bit of a vague explanation but it's really hard to debug as it's so hard to reproduce the problem. It's a bit of a vague bug as well.

Hope anyone can help us with this issue...

Thanks,
Jan

Latest version of PDFNet should correct this issue.

Contact support at pdftron.com to get the latest iOS SDK link.

Ryan,

I'm also experiencing this issue using PDFNet SDK 6.7.3 (56298). In addition to the behavior Jan detailed above. If you continue to try and use the same instance of PDFViewCtrl, eventually the view will turn black and documents will no longer appear to render.

The following logs were found when the even occurred, our usage is stock and no gestures have been added to the view:

2017-05-23 15:45:30.979 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch
2017-05-23 15:45:31.563 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch
2017-05-23 15:45:32.145 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch
2017-05-23 15:45:32.996 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch
2017-05-23 15:45:33.163 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch
2017-05-23 15:45:33.579 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch
2017-05-23 15:45:33.929 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch
2017-05-23 15:45:34.197 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch
2017-05-23 15:45:35.396 VEO Mobile[9473:3633734] <_UISystemGestureGateGestureRecognizer: 0x17418a1b0>: Gesture: Failed to receive system gesture state notification before next touch

Are these issues file specific, or can you reproduce with any PDF file?
Does it only occur on devices, or simulator also?
What devices have you reproduced on?

Ryan,

Thanks for responding so quickly. This issue has happened once in the simulator but due to gesture controls I’ve not found it to be easy to trigger there. We’ve been able to repro it on an iPad Air 1 and iPad Air 2 but it appears to be a timing issue. Our ability to trigger it increases if we race the view controller by attempting to zoom (by pinch gesture and/or double tap) before the page has finished rendering. In most cases this is right after setting the document property on the PTPDFViewCtrl instance.

This has happened on multiple documents. Most of them are small in size < 12MBs, but they are architectural diagrams containing a lot of vectors that need to be rendered, some of them also include link annotations.

Unfortunately the documents that’ve triggered this issue, we are not at license to share as they are customer data. I will attempt to followup with our customer solutions team to see if it’s possible to either get permission to pass some along or to create documents that we can also reproduce the issue with.

Thanks,
Robert

It would help a lot if you could make a video demonstrating the issue. Perhaps you could make 2 or 3, so we can get the best idea of what might be happening.

Also, are you able to reproduce using our unmodified SDK sample? Or does it only happen in your project?