-
Notifications
You must be signed in to change notification settings - Fork 185
Description
Runtime "couldn't find DSO to load" errors appear to be rather common, with a myriad of possible causes, some of which only surface in production, and some of which are specific to specific versions of Android or specific architectures.
The errors don't give any clue as to the cause and there are dozens and dozens of issues around errors like this:
couldn't find DSO to load: libhermes.so
Since this is a common, known problem (common enough that Google have an FAQ on it), it'd be great if we could have some standard troubleshooting docs:
- What these errors mean
- What diagnostics to do (e.g. how to check if the not found packages are in the bundle)
- Things to try (e.g. check ProGuard isn't removing the packages, check the dependencies are added correctly... many more)
Currently the debugging experience for this common error involves wading through dozens of issues with identical error messages, each of which point to dozens of isolated lines of config to check (many of which are specific to specific versions or environments), without any overall sense of the bigger picture of what the error means and what exactly the required pieces are for SoLoader to work properly.