The game won't start on Android

Good afternoon, next problem. On my Mi 9T Pro phone, my game starts without problems, but having given access to it to friends, I encountered the problems listed below, can anyone suggest what to try or what additional information to provide? I think that the problem lies in the incorrectly set Android packaging parameters. I load the game via ABB file. Used packaging method for ETC2 project

 FATAL EXCEPTION: main
    Process: com.----------------------------, PID: 17348
    java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "fgets_unlocked" referenced by "/data/app/com.---------------------------------------
``GBXLxTsA3uZimBeNfMnpmg==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libUE4.so"...
    	at java.lang.Runtime.loadLibrary0(Runtime.java:1016)
    	at java.lang.System.loadLibrary(System.java:1657)
    	at com.epicgames.ue4.GameActivity.<clinit>(Unknown Source:381)
    	at java.lang.Class.newInstance(Native Method)
    	at android.app.Instrumentation.newActivity(Instrumentation.java:1180)
    	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2829)
    	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3030)
    	at android.app.ActivityThread.-wrap11(Unknown Source:0)
    	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
    	at android.os.Handler.dispatchMessage(Handler.java:105)
    	at android.os.Looper.loop(Looper.java:164)
    	at android.app.ActivityThread.main(ActivityThread.java:6938)
    	at java.lang.reflect.Method.invoke(Native Method)
    	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
    	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
FATAL EXCEPTION: main
Process: com.---------------------------, PID: 26277
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "fgets_unlocked" referenced by "/data/app/com.---------------------------------------AH01Np4VByEmo5DROwgWMw==/split_config.armeabi_v7a.apk!/lib/armeabi-v7a/libUE4.so"...
	at java.lang.Runtime.loadLibrary0(Runtime.java:1016)
	at java.lang.System.loadLibrary(System.java:1657)
	at com.epicgames.ue4.GameActivity.<clinit>(Unknown Source:381)
	at java.lang.Class.newInstance(Native Method)
	at android.app.Instrumentation.newActivity(Instrumentation.java:1174)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2696)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2883)
	at android.app.ActivityThread.-wrap11(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1613)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6523)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:857)

At the moment, an approximate solution has been found, the problem was that the NDK version indicated latest, after replacing it with android-19, the problem went away. Can anyone explain how this could affect ABB’s split system?