[$250] Attachment - The app crashes when attempting to open larger specific pdf

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 1.4.65-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:(https://expensify.testrail.io/index.php?/tests/view/4510570&group_by=cases:section_id&group_order=asc&group_id=292107)
Email or phone of affected tester (no customers): shussain+accoun1@applausemail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. On a conversation, click on the + button in the compose box
2. Upload attached larger pdf to a conversation
3. Then click on it to preview

Expected Result:

Attachment should be displayed in preview

Actual Result:

The app crashes when attempting to open larger specific pdf

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6460367_1713968986182.WhatsApp_Video_2024-04-24_at_19.23.10.mp4

Bug6460367_1713968986208!class-9-maths-chapter-10-solutions-2024-02-08_22_17_00.194.pdf

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01efa7ba36a86bb510
• Upwork Job ID: 1783189054673006592
• Last Price Increase: 2024-05-01

[melvin-bot]

Triggered auto assignment to @arosiclair (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @lschurr (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01efa7ba36a86bb510

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia (External)

[mountiny]

I dont see anything specific in the checklist that could influence PDF updates

[mountiny]

It seems like its related to this crash logs

Fatal Exception: com.facebook.jni.CppException: JSON Parse error: Unexpected end of input

SyntaxError: JSON Parse error: Unexpected end of input
    at parse (native)
       at com.swmansion.reanimated.nativeProxy.EventHandler.receiveEvent(EventHandler.java)
       at com.swmansion.reanimated.nativeProxy.EventHandler.receiveEvent(EventHandler.java:25)
       at com.facebook.react.uimanager.events.Event.dispatch(Event.java:167)
       at com.swmansion.reanimated.NodesManager.handleEvent(NodesManager.java:328)
       at com.swmansion.reanimated.NodesManager.onEventDispatch(NodesManager.java:314)
       at com.facebook.react.uimanager.events.FabricEventDispatcher.dispatchEvent(FabricEventDispatcher.java:42)
       at com.facebook.react.fabric.interop.InteropEventEmitter.receiveEvent(InteropEventEmitter.java:50)
       at org.wonday.pdf.PdfView.loadComplete(PdfView.java:151)
       at com.github.barteksc.pdfviewer.listener.Callbacks.callOnLoadComplete(Callbacks.java:83)
       at com.github.barteksc.pdfviewer.PDFView.loadComplete(PDFView.java:830)
       at com.github.barteksc.pdfviewer.DecodingAsyncTask.onPostExecute(DecodingAsyncTask.java:90)
       at com.github.barteksc.pdfviewer.DecodingAsyncTask.onPostExecute(DecodingAsyncTask.java:27)
       at android.os.AsyncTask.finish(AsyncTask.java:755)
       at android.os.AsyncTask.access$900(AsyncTask.java:192)
       at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
       at android.os.Handler.dispatchMessage(Handler.java:107)
       at android.os.Looper.loop(Looper.java:264)
       at android.app.ActivityThread.main(ActivityThread.java:7684)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)

[melvin-bot]

📣 @Engr-Shoaib! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[melvin-bot]

⚠️ Invalid email. Please make sure to create an Expensify account with this email first here.

[mountiny]

I have tested uploading some pdf files and did not encounter the crash. I have informed SWM to look into the crash tomorrow, I think we can demote as there are no clear reproduction steps, seems like it might be specific to device or the file

[Engr-Shoaib]

Yes I also try this feature but it's work properly.

…

On Thu, Apr 25, 2024, 2:50 AM Vit Horacek ***@***.***> wrote: I have tested uploading some pdf files and did not encounter the crash. I have informed SWM to look into the crash tomorrow, I think we can demote as there are no clear reproduction steps, seems like it might be specific to device or the file — Reply to this email directly, view it on GitHub <#40925 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCR2A42Y374QUFQUB6C5YBTY7ASMDAVCNFSM6AAAAABGXLJEGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVHEYDMOBTGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[arosiclair]

No proposals for now. Doesn't seem like any of us have reproduced either.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[lschurr]

Cool, let's close since we aren't able to reproduce.