react-native-pdf
react-native-pdf copied to clipboard
When sliding through the PDF file, closing the current page causes the app to crash.
What react-native
version are you using?
0.72.4
What react-native-pdf
version are you using?
6.7.5
What platform does your issue occur on? (android/ios/both)
android
Describe your issue as precisely as possible :
- When sliding through the PDF file, closing the current page causes the app to crash. The crash details are as follows:
E FATAL EXCEPTION: PDF renderer Process: com.sssss, PID: 12594 java.lang.IllegalStateException: Already closed at io.legere.pdfiumandroid.util.ConfigKt.handleAlreadyClosed(Config.kt:20) at io.legere.pdfiumandroid.PdfPage.close(PdfPage.kt:582) at kotlin.io.CloseableKt.closeFinally(Closeable.kt:56) at io.legere.pdfiumandroid.PdfiumCore.renderPageBitmap(PdfiumCore.kt:406) at com.github.barteksc.pdfviewer.PdfFile.renderPageBitmap(PdfFile.java:301) at com.github.barteksc.pdfviewer.RenderingHandler.proceed(RenderingHandler.java:109) at com.github.barteksc.pdfviewer.RenderingHandler.handleMessage(RenderingHandler.java:66) at android.os.Handler.dispatchMessage(Handler.java:117) at android.os.Looper.loopOnce(Looper.java:205) at android.os.Looper.loop(Looper.java:293) at android.os.HandlerThread.run(HandlerThread.java:110)
Show us the code you are using?
return (
<View style={styles.container}>
{fileUri && (
<Pdf
trustAllCerts={false}
style={styles.pdfStyle}
source={getFileSource()}
onLoadComplete={(numberOfPages, filePath) => {
console.log(Number of pages: ${numberOfPages}
);
}}
onPageChanged={(page, numberOfPages) => {
console.log(Current page: ${page}
);
}}
onError={error => {
console.error(error);
}}
/>
)}
</View>
);
I'm facing the same issue, any suggestion?
I am facing the same issue any solution?
Also facing this, but a different error:
java.lang.RuntimeException: Loaded page is null
io.legere.pdfiumandroid.PdfDocument.nativeLoadPage(Native Method)
io.legere.pdfiumandroid.PdfDocument.openPage(PdfDocument.kt:83)
io.legere.pdfiumandroid.PdfiumCore.renderPageBitmap(PdfiumCore.kt:406)
com.github.barteksc.pdfviewer.PdfFile.renderPageBitmap(PdfFile.java:301)
com.github.barteksc.pdfviewer.RenderingHandler.proceed(RenderingHandler.java:109)
com.github.barteksc.pdfviewer.RenderingHandler.handleMessage(RenderingHandler.java:66)
android.os.Handler.dispatchMessage(Handler.java:106)
android.os.Looper.loopOnce(Looper.java:201)
android.os.Looper.loop(Looper.java:288)
android.os.HandlerThread.run(HandlerThread.java:67)
same issue here.
my workaround: downgrade from 6.7.5 to 6.6.2.
I have temporary solution to fix it, hope this issue will be fixed ASAP.
- Downgrade to 6.7.4
- Create patch file from our project and apply the fix from this PR: https://github.com/wonday/react-native-pdf/pull/827
- re-run
npm install
to apply the patch, crash issue resolved.
Having the same problem here, and also this one :
Fatal Exception: java.lang.RuntimeException: Get page pdf document null at io.legere.pdfiumandroid.PdfDocument.nativeLoadPage(PdfDocument.kt) at io.legere.pdfiumandroid.PdfDocument.openPage(PdfDocument.kt:83) at io.legere.pdfiumandroid.PdfiumCore.renderPageBitmap(PdfiumCore.kt:406) at com.github.barteksc.pdfviewer.PdfFile.renderPageBitmap(PdfFile.java:301) at com.github.barteksc.pdfviewer.RenderingHandler.proceed(RenderingHandler.java:109) at com.github.barteksc.pdfviewer.RenderingHandler.handleMessage(RenderingHandler.java:66) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:214) at android.os.HandlerThread.run(HandlerThread.java:65)
Any clue on how to fix this ?
my workaround: downgrade from 6.7.5 to 6.6.2.
tested, working on my project
does u guys facing an error while the component finished loading and then the app suddenly crashed? i've been searching for this and got no answer
Any idea how to fix this one? For me the "already closed" issue is raised when user enters pdf screen and then goes to other place in the app - when he comes back to pdf the app crashes with this error.
Is their any solution available for this? I cannot see any potential fix to this currently. Also, downgrading the version does not seems like a fix to this error.
downgrade to 6.6.2 works for me