Android Question B4A version 13.4 Breaks my App

walterf25

Expert
Licensed User
Longtime User
Hi all, I just updated my B4A version to the latest 13.4, and for some reason my app compiles and it gets installed OK but the app exits without giving me any errors, This is very strange as my app was compiling just fine before I updated the B4A version, I downloaded the command line tools and resources as I always do with every new update, Not sure what the issue is as I don't see any errors in the logs, however when I open Android Studio and filter the logs by my package name I see the following, but not sure if this is what is actually causing the crash.

The only Errors I see in these logs that I believe may be causing this issue are the following lines

But then I don't know where that .so file would come from, and as I mentioned, the app was compiling just fine before I updated the B4A version and I have not done any changes to this app in months, has anyone else had any issues with their apps after updating to the latest version?
 
Sort by date Sort by votes

aeric

Expert
Licensed User
Longtime User
I think the error is here.
B4X: 
2025-11-11 03:41:37.887 16942-16942 libc com.strom.ellustros A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4d9976836157bc in tid 16942 (strom.ellustros), pid 16942 (strom.ellustros)

Make sure to clean install the Android SDK.
 
Upvote 0

walterf25

Expert
Licensed User
Longtime User
I dont even know how to decode whatever that error means
And I did made sure I did a clean install of the Android SDK
 
Upvote 0

aeric

Expert
Licensed User
Longtime User
walterf25 said:
I dont even know how to decode whatever that error means
And I did made sure I did a clean install of the Android SDK
Click to expand...
I also made a guess here. Something may crashed in the memory due to the SDK changes.
It maybe also related to private sign key, security or encryption library.
 
Upvote 0

walterf25

Expert
Licensed User
Longtime User
aeric said:
I also made a guess here. Something may crashed in the memory due to the SDK changes.
It maybe also related to private sign key, security or encryption library.
Click to expand...
Why do you think it may be the private sign key or encryption library?
 
Upvote 0

aeric

Expert
Licensed User
Longtime User
walterf25 said:
Why do you think it may be the private sign key or encryption library?
Click to expand...
OK if it is about the penguin then it may related to the AR/VR library you are using.

From Google search AI Overview:

The error "libpenguin.so not found" indicates that a shared library file, libpenguin.so, is missing from the expected location on an Android device or within an Android application's build environment. This typically occurs in projects involving Unity, Android Studio, and potentially AR/VR packages like ARCore or AR Foundation.
Possible causes and solutions:
  • Missing or incorrectly packaged library:
    • The libpenguin.so file might not be included in the Android application package (APK) or is not being correctly installed on the device.
    • Solution: Ensure that the library is properly declared in your project's build settings (e.g., AndroidManifest.xml or build.gradle for Android Studio, or within Unity's build settings if applicable) so that it is included in the final build.
  • Incorrect library path:
    • The application might be looking for libpenguin.so in a location where it does not exist.
    • Solution: Verify the expected path for native libraries within your application's code and ensure that libpenguin.so is placed in that location during the build process or installed to the correct system directory if it's a pre-installed library.
  • Cross-platform compatibility issues:
    • If the project was developed on a different operating system (e.g., macOS) and then moved to another (e.g., Windows), there might be issues with how native libraries are handled or transferred.
    • Solution: Rebuild the project specifically for the target platform to ensure all necessary libraries are correctly compiled and included.
  • AR/VR package dependency issues:
    • libpenguin.so might be a dependency of an AR/VR package (like ARCore) that is not being correctly included or linked.
    • Solution: Check the documentation for the specific AR/VR package you are using to ensure all necessary setup steps for native libraries are followed. This might involve configuring package settings within Unity or Android Studio.
  • Build system configuration problems:
    • Issues with the build system (e.g., CMake in Android Studio) can prevent native libraries from being correctly built or linked.
    • Solution: Review your build system configuration (e.g., CMakeLists.txt or build.gradle) to ensure that libpenguin.so is properly referenced and built.
Troubleshooting steps:
  • Check logcat output:
    Examine the logcat output from the Android device or emulator for more detailed error messages that might provide clues about why libpenguin.so is not found.
  • Verify file existence:
    Manually check the contents of your APK or the device's file system to confirm whether libpenguin.so is present in the expected location.
  • Clean and rebuild:
    Perform a clean build of your project to ensure all dependencies are resolved and rebuilt correctly.
 
Upvote 0
You must log in or register to reply here.
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…