Armv7 Vs Arm64 Android

[Antígona Knknown]

Ihave the same problem. The following work around seems to work for me when this starts up. I turn off arm64 and compile only for armv7. I then turn arm64 back on and compile for both arm64 and armv7 and then it works. This is in Unity 2021.1.10f1. This problem of crashing seems to randomly start at some point, and then I have to do the above to get it back to normal.

I was just now able to export several runnable builds with intermediate changes in the code. I had previously deleted the library folder in the project folder once and now it seems to work. CAUTION: All assets will be re-imported and it may be necessary to switch back to the previous platform, also the project must be closed when deleting the folder. Otherwise, everything worked fine for me, even the project settings were all preserved.

I can confirm that just removing the Library/il2cpp* folders will resolve the issue. Happens frequently when switching between architecture types, for example going from a Mono/ARMv7 Build to a IL2CPP/ARMv7+ARM64 build.

Hey guys, this bug also drive me crazy. But I found if export gradle project and generate apk or aab in Android Studio will be fine. Seems that there are some differences between Unity build and AS build.

How does the res dir work for ARM64 android in native extensions? I have the following file structure and if I make a 32+64bit build, only the files in fmod/res/armv7-android end up in the final APK. The 64-bit libraries are not copied.

I have successfully compiled the source code with demo main.cpp as a so library and ran that library using unity android. But the compilation works for armbi-v7a but not for arm64-v8a. Because some codes of the cmsis core include are written specific for 32 bit not for 64 bit. So need support for 64 bit so that can compile for all the android devices.

Hi Shawn, Do you have updates from the engineering team.

We are facing the same issue with Android for arm64-v8a. Especially now that Android 14 officially only supports 64 bits and have dropped all 32 bits.

I am trying hdf5-1.10.6 with autoconf and cmake; the cmake completed the configuration with android clang 9.0.1 based toolchain set in environment. Then during the make phase failed fast. Before giving up, the script produced two binaries for the target system:

Crossing HDF5 Clib is tedious process, and in most cases can be avoided by installing gcc on the target platform, then compiling the library. For people with armv7 with hardware float I uploaded the compiled binaries: hdf5-1.10.6-arm7f.tar.gz (4.9 MB)

3a8082e126