App freezes on Scene change

when I click the button that leads to the next scene it just freezes .
when i build the apk and paste it to my phone and run it, it freezes when loading next scene but when i build and run directly from unity it loads the next scene and works fins.
i tested with empty scene and tried with different devices and still the same problem. also tried building apk with development build.
i connected logcat and got these error when i click on the bottom that loads to next scene:

Error:
Unity Services: An error occurred while trying to get the project configuration for services.

  • Couldn’t fetch config file: The game couldn’t find the UnityServicesProjectConfiguration.json file at the expected location within your built APK.
  • URL: The error specifies the location it tried to access - jar:file:///data/app/~~b5tEjePaAMeMvSKo5aXAQw==/com.GCS.egyptrunner-VYtIRtjZuAKWtHxxS7xxKg==/base.apk!/assets/UnityServicesProjectConfiguration.json
  • Reason: HTTP/1.1 404 Not Found - This indicates the file wasn’t found at the specified location

Gemini said this file should be in the assets folder, i found this file in another directory so i copied it in the assets folder and the built the apk and the problem still exist, it freezes on next scene load.

then I looked to other errors in logcat : (and this is Gemini analysis)
Errors Before Clicking the Button:

  • ding:background Not starting debugger since process cannot load the jdwp agent. (Error)

  • This error seems related to debugging and might not directly affect your app’s functionality. It indicates an issue with starting the debugger because the process cannot load the Java Debug Wire Protocol (JDWP) agent. You can likely ignore this for now unless you’re actively debugging the app.

  • libc Access denied finding property “persist.vendor.sys.activitylog” (Error)

  • This error suggests the app might be trying to access a system property (persist.vendor.sys.activitylog) that it doesn’t have permission for. This property might be related to logging behavior.

  • Solutions:

  • Check your app’s manifest file and remove any unnecessary permissions related to system properties.

  • If this permission is truly required for your app’s functionality, consult the documentation for your specific device or target Android version to understand the appropriate way to access this property.

  • IMGMemtrackHAL GetGLMemtrackRecords: Subtracting per-pid stats from global stats would wrap. Clamping global stats to zero. (Error)

  • This error originates from the graphics memory tracking system and seems related to potential memory tracking inconsistencies. It might not directly cause a crash but could indicate issues with memory management.

  • Solutions:

  • Profile your app’s memory usage using Unity’s profiler or Android Studio’s profiling tools to identify areas where memory usage might be high.

  • Optimize your game’s memory usage by reducing unnecessary memory allocations and disposing of unused objects properly.

Errors After Clicking the Button (Scene Load):

  • FbnsAIDLClientManager Errors (Multiple lines):

  • These errors indicate a problem with binding to a service called FbnsAIDLService. This service might be related to push notifications or other functionalities. The errors suggest the app is unable to establish a connection with the service.

  • Solutions:

  • If your app doesn’t rely on push notifications or functionalities that require this service, you can likely ignore these errors.

  • If these services are essential, ensure they are properly configured and running on the device. Consult the documentation for the specific service or library you’re using for guidance on troubleshooting binding issues.

  • IMGMemtrackHAL GetGLMemtrackRecords: Subtracting per-pid stats from global stats would wrap. Clamping global stats to zero. (Error) (Same as before)

  • This error appears again, suggesting potential memory tracking inconsistencies. Refer to the solutions mentioned previously for addressing memory management.

  • MtkDataShapingUtils Exception openLteGateByDataShaping in java.lang.NullPointerException: null receiver (Error) (Same as before)

  • This error is identical to the one encountered earlier and points to a problem within the Android system related to data shaping functionalities. There’s not much you can directly fix within your app for this system-level issue.

  • Solutions (limited):

  • Consider reporting the issue to the device manufacturer or the developer community for your specific device model, as suggested earlier.

  • PhoneInterfaceManager [PhoneIntfMgr] getCarrierPackageNamesForIntent: No UICC (Error)

  • This error indicates the system couldn’t find a SIM card (UICC) in the device. This might not directly cause the scene loading freeze, but it’s good to be aware of.

  • MtkDataShapingUtils Exception openLteGateByDataShaping in java.lang.NullPointerException: null receiver (Error) (Same as before)

  • This repeated error highlights the data shaping issue again.

but these errors don’t seem related to why it works in build and run and doesn’t load in build.

please help

turns out i just had to uncheck split application binaries in player settings

1 Like