APPs crash in 64bit only device

tracyhuangyingxia commented 7 months ago

Checklist before submitting a bug report

[X] I've updated to the latest released version of the SDK
[X] I've searched for existing Github issues
[X] I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group
[X] I've read the Code of Conduct
[X] This issue is not security related and can safely be disclosed publicly on GitHub

Java version

NA

Android version

Android 14

Android SDK version

33

Installation platform & version

im.kumu.ph, com.xb.topnews

Package

Core & AppEvents

Goals

Please compatible with 64bit only models to avoid this exception.

Expected results

Apps can be launched normally in 64bit only device

Actual results

APPs crash https://drive.google.com/file/d/15NIAWgRkcV1G2CGoGhAeM4ZQXkfqr9qt/view?usp=sharing

Steps to reproduce

Install the apps--open the app--Observe

Code samples & details

// INSERT YOUR CODE HERE

tracyhuangyingxia commented 7 months ago

Hi Team,

Here is the devs comment:

The root cause of this order is the logic problem of Facebook sdk soloader shown in the stack. However, the triggering factors are as follows:

The running model is a 64bit only model. The system shared library only has the system/lib64 directory and no system/lib directory.

When the application is installed as a bulk package, it relies on the system's so library, which is not stored in data/app/xxxx/lib/arm64 according to the normal installation path, but exists in the application's private data directory data/user/0/xxxxx /lib-0

After the above conditions are met, facebook sdk will judge on its own the lack of dependent system/lib/catalog files and throw an exception, and the stack will not be called to the system level.

tracyhuangyingxia commented 6 months ago

Hi team,

We've found other apps that crash on 64bit-only device, could you please help us look at this issue.

Thank you in advanced.

facebook / facebook-android-sdk