`page` prop not being respected

[harveyappleton]

I used the page prop on react-native-pdf to render specific pages from the pdf as follows:

<Pdf
                  source={{ uri: pdfUrl, cache: false }}
                  page={index + 1}
                  singlePage
                  enablePaging={false}
                  scrollEnabled={false}
                  scale={1}
                  minScale={1}
                  maxScale={1}
                  showsHorizontalScrollIndicator={false}
                  showsVerticalScrollIndicator={false}
                  enableAnnotationRendering={false}
                  enableDoubleTapZoom={false}
                  style={{ height: 135, width: isMobile ? 90 : 180, zIndex: 0 }}
                />

However the page prop doesn't seem to work any more?
I noticed that you can use the ref approach and call .setPage on that, but it was easier when we could pass page prop into it (particularly when dealing with arrays of pdf pages).

[harveyappleton]

Hey @126punith - any thoughts on this one?

[126punith]

Thanks for the clear repro and ping.

We’ve traced a few likely causes: the JS wrapper today only refreshes the file when the source URI changes in componentDidUpdate, not when page alone changes—so controlled updates from a list (page={index + 1}) may not always force native navigation. There may also be a race on Android where onPageChanged updates internal state around the same time as a prop-driven jump, and on iOS navigation is conditional on document load and prop diff state.

We’re going to add an explicit sync when page changes after the PDF is loaded, review Android/iOS native guards, and fix an internal issue where the JSI branch of setPage() used a one-off id instead of a stable pdfId.

Until a release ships, using the ref + setPage() remains a reliable workaround; we’ll update this issue when the fix is merged.