Search Issue Tracker
Fixed
Fixed in 2021.3.44f1, 2022.3.45f1, 6000.0.17f1, 7000.0.0a1
Votes
0
Found in
2021.3.42f1
2022.3.40f1
6000.0.14f1
7000.0.0a1
Issue ID
UUM-77679
Regression
No
[Android] “libNativeMemoryBinary.so” is not being generated when exporting the project
Reproduction steps:
1. Open the attached “armeabi_repro.zip“ project
2. Open the Build Settings (File > Build Settings…)
3. Make sure that the “Android” platform is selected
4. Enable Export Project in the Build Settings
5. Export
6. Open the armeabi-v7a folder in the exported project (exported_project/unityLibrary/src/main/jniLibs/armeabi-v7a) and observe it
Expected result: “libNativeMemoryBinary.so” file exists in armeabi-v7a folder
Actual result: “libNativeMemoryBinary.so” file does not exist in armeabi-v7a folder
Reproducible with: 2021.3.42f1, 2022.3.40f1, 6000.0.14f1
Reproduced on: Windows 11 Pro, macOS 14.5 (Intel)
Not reproduced on: no other environment tested
Notes:
- Reporter noted that platform settings of "Packages/NativeMemeory/Runtime/Libs/Android/armeabi-v7a/libNativeMemoryBinary.so" file show this line: "CPU:ARMv7, Shared Library Type: Executable" which shows that file should be included in the exported project
- Reporter noted that .meta file of armeabi-v7a/libNativeMemoryBinary.so does not actually include the platform settings but the Editor reports it as ARMv7 anyway. This does not fail the build process but causes unexpected issues after the application goes live
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
Add comment