[$4000] Identify source and fix crash: com.facebook.soloader.SoLoader.doLoadLibraryBySoName

[melvin-bot]

Fatal Exception: java.lang.UnsatisfiedLinkError

couldn't find DSO to load: libhermes.so

SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.expensify.chat/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/~~TQymoaD6lIwlgPXCQPi3Tw==/com.expensify.chat-dV5g1giPTUH-ZkSuaAJlog==/lib/arm64 flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
Native lib dir: /data/app/~~TQymoaD6lIwlgPXCQPi3Tw==/com.expensify.chat-dV5g1giPTUH-ZkSuaAJlog==/lib/arm64

result: 0

SoLoader.java line 918 com.facebook.soloader.SoLoader.doLoadLibraryBySoName

Number of Crashes: 90

Device Information

• Platforms: Android
• App Versions: 1.1.82-5
• Devices: samsung SM-A326B 11

Stacktraces

Android 1.1.82-5

com.facebook.soloader.SoLoader.doLoadLibraryBySoName (SoLoader.java:918)
com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl (SoLoader.java:740)
com.facebook.soloader.SoLoader.loadLibraryBySoName (SoLoader.java:654)
com.facebook.soloader.SoLoader.loadLibrary (SoLoader.java:634)
com.facebook.soloader.SoLoader.loadLibrary (SoLoader.java:582)
com.facebook.hermes.reactexecutor.HermesExecutor.<clinit> (HermesExecutor.java:20)
com.facebook.hermes.reactexecutor.HermesExecutorFactory.create (HermesExecutorFactory.java:29)
com.facebook.react.ReactInstanceManager$5.run (ReactInstanceManager.java:1066)
java.lang.Thread.run (Thread.java:923)

---

Internal Firebase Info

💥 DO NOT EDIT THIS SECTION 💥

Crash IDs: 3851f750a3551753cfd665e72607ec8b
Exception: couldn't find DSO to load: libhermes.so SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.expensify.chat/lib-main flags = 1] SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/~~TQymoaD6lIwlgPXCQPi3Tw==/com.expensify.chat-dV5g1giPTUH-ZkSuaAJlog==/lib/arm64 flags = 0] SoSource 2: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2] SoSource 3: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2] Native lib dir: /data/app/~~TQymoaD6lIwlgPXCQPi3Tw==/com.expensify.chat-dV5g1giPTUH-ZkSuaAJlog==/lib/arm64 result: 0

[melvin-bot]

Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

Still overdue 6 days?! Let's take care of this!

[melvin-bot]

Triggered auto assignment to @dylanexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[dylanexpensify]

Update coming today!

[dylanexpensify]

@marcaaron could I get an updated title for this issue so I could get it on Upwork? Thanks man!

[marcaaron]

All of these can probably just be renamed to Identify source and fix crash: [crash name]

[dylanexpensify]

Nice, thanks man!

[dylanexpensify]

Internal: https://www.upwork.com/ab/applicants/1557661553099186176/job-details
External: https://www.upwork.com/jobs/~0144dd7c56faead9c1

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (Exported)

[kevinksullivan]

@dylanexpensify are we going ahead with doubling? Also, @luacmartins should we be adding the Needs Reproduction label here? Or how can we work on making this a more actionable issue?

[dylanexpensify]

Doubled, posted in #expensify-bugs here!

[rushatgabhane]

this needs reproduction steps

when was the last crash?

[JmillsExpensify]

@luacmartins To help clear out the extensive backlog of /App bugs, we're putting the spotlight on all bugs older than 4 weeks old. To help unblock the roadmap and get our bug pipeline back in equilibrium, can you:

• Decide whether any proposals currently meet our guidelines and can be approved as-is
• For any that can't, please take this issue internal and treat it as one of your highest priorities
• If you have any questions, don't hesitate to start a discussion in #bug-zero

Thanks everyone!

[furkanuzundev]

Hello guys,
I'm trying to detect issue almost 2 days, but it's looking weird.Here's steps;

1 - First of, i think that issue coming from com.facebook.soloader.SoLoader so i've updated it to the last version but nothing changed. https://github.com/facebook/SoLoader
2 - And then I kept searching. I tried to find exactly where the error was throwing. And it looks exactly like this;
https://github.com/facebook/SoLoader/blob/cc16d8960ece7e4c63de4bb22c086ed753280cc3/java/com/facebook/soloader/SoLoader.java#L1055

    try {
      if (sSoSources == null) {
        Log.e(TAG, "Could not load: " + soName + " because no SO source exists");
        throw new UnsatisfiedLinkError("couldn't find DSO to load: " + soName);
      }
    }

SoLoader is a native code loader for Android.But as you can see, it can't load the module that missing.

3 - I reviewed some issues and realized that a lot of people experienced this problem, especially after 0.64. Especially those who updated 0.70 saw this error frequently in the firebase console. You can review the references here:

facebook/react-native#35374
facebook/react-native#35323
facebook/react-native#35264
facebook/react-native#35222
facebook/react-native#35201
facebook/react-native#34089
facebook/react-native#33495

4 - Finally, I tried creating a react native application from scratch. If the problem is caused by the current state of the application, the application we created from scratch should be running without errors.

But what is that?

Probably the error is from hermes.

In the new architecture, we no longer use hermes as an npm package, but as an embedded. Therefore, we cannot make any changes to the package.

Also, the error only shows itself between Android 6-12 and .release version.

[Santhosh-Sellavel]

How to reproduce this one consistently @furkanuzundev ?

[furkanuzundev]

@Santhosh-Sellavel

1 - create a new device from android studio before version 12.
2 - type react-native run-android --variant release on console
3 - Open Logcat from android studio, select debuggable phone and error section from combobox.
4 - Search couldn't find DSO to load to find error.

[Santhosh-Sellavel]

Cool, I am asking if can we get this reproduced on the live app.

[furkanuzundev]

@Santhosh-Sellavel If we can try correct version, why not? But as i remember, firebase has delay while pushing error on console.if so, it might cause some trouble.

[furkanuzundev]

By the way @Santhosh-Sellavel, app is not crush and closing completely as i'm tested.It's just throwing an error on console while opening.

[dylanexpensify]

@luacmartins can you comment on this request?

[luacmartins]

Coming back from ooo today, I posted an update here asking for more opinions on my decision. I'll come back to this issue this afternoon.

[luacmartins]

Coming from that Slack thread. We will close this issue since:

1. It seems like there's no crash and it doesn't affect users
2. The error comes from hermes, but we no longer use it as an npm dependency, hence we can't fix the error. Hermes must be loaded as a peer dependency.
3. The console error only shows up for older versions of android 6-12

@dylanexpensify let's pay @furkanuzundev for the investigation they did here and close the issue once done!

[trjExpensify]

@dylanexpensify is out for the rest of the week. I'll reassign to myself to handle that, discussing internally here. Also going to assign @furkanuzundev for posterity.

[melvin-bot]

📣 @furkanuzundev You have been assigned to this job by @trjExpensify!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[trjExpensify]

@furkanuzundev I've sent you a contract in Upwork. Let me know once you've received it and I'll close this out.

[furkanuzundev]

@trjExpensify I accepted the contract. Thank you @Santhosh-Sellavel, @luacmartins for your efforts!

[trjExpensify]

Perfect, settled!

[dreamGitBhargav]

Did you find any solution?

[MelvinBot]

📣 @dreamGitBhargav! 📣

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. 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.
2. 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.
3. 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>

[Linuhusainnk]

any solutions?

[melvin-bot]

📣 @Linuhusainnk! 📣
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>