Hadi Tavakoli

AIRSDKMANAGER logs: ``` ADT 50.2.4.3 called with: -version ADT 50.2.4.3 called with: -package -target apk-debug -listen 7936 -arch armv8 -storetype PKCS12 -keystore /.../app/cert/android.keystore -storepass xxxxxx /.../app/out/xxx.apk /.../app/out/application.xml -extdir /.../app/ane -C...

Thanks for check the app @ajwfrost We have more info now! So, more and more "remote" testing has been done and now we have a new clue which explains why...

We have checked almost all SDK versions. the problem is still there. And just right now, we tested `50.2.4.2` released yesterday and it's still there. Besides the Samsung devices, we...

Correct, I started testing with 51.2.1.5 and don't know the earlier ones. To be exact, switching back to 51.1.3.10 is the last good thing. And yes, the test is isolated...

@marchbold Here is my build script: ``` #!/bin/sh clear export PATH=$PATH:$1 adt -package -target ipa-app-store \ -storetype PKCS12 \ -keystore $3/$5 \ -storepass $6 \ -provisioning-profile $3/$7 \ $2/App.ipa \...

Update: I didn't have hope to see any difference but updated to 51.2.1.6 to see if anything has changed. unfortunately the same is happening. can't use this SDK for production...

Ok, have not been updating AIR SDK and ANEs for a while because of this issue, but today I updated the project to `51.2.2.4` without touching the ANEs and the...