airsdk/Adobe-Runtime-Support

The apk encountered a startup crash exception which compiled by 51.1.2.1 window version

Opened this issue · 14 comments

We did not catch any exceptions through logcat.But provided a video.Everything is ok at 50.2.3.4 window version.but upgrade to 51.1.2.1 window version,an error has occurred.
Uploading 51.1.2.1_win_ver_startup_exptions.mp4.zip…

Hi

I think you posted the message before the video finished uploading.. I can't get at the zip there?

But just to check given your previous message, is this happening when you're using a custom/updated version of the runtimeClasses.jar file that I uploaded to the other ticket? That file can't be used in other versions of the SDK..

thanks

So just to check .. if you build an application with the standard AIR SDK 51.1.2.1, for Android, it's not starting up? Can you please provide the logcat output for it (we can potentially see what's happening via what doesn't appear in the log, as much as what does appear). Plus can you confirm what device and Android OS version you're using? We don't see an issue when testing here so it may be something related to the OS/device..

thanks

I will collect information and provide feedback.
But another bug occurred the APK file which packaged by AIR SDK 51.1.2.1 can not be installed on Android 15 by adb install cmd .The error log is as follows.

{
"steps": [
{
"name": "launch"
},
{
"name": "monkey"
},
{
"name": "uninstall",
"result": "FAILED",
"detail": "Failure [DELETE_FAILED_INTERNAL_ERROR], "
},
{
"name": "install",
"result": "FAILED",
"detail": "Performing Streamed Install, adb: failed to install /tmp/.omni/apks/1108173915_30170388_0195675c25ac14840a195f251ed537c26d44d78ac.apk: cmd: Can't find service: package"
}
],
"installTimeConsuming": 1.00779294967651,
"launchTimeConsuming": 0,
"screenshots": []
}

error-spash-crash.txt

This is a log of app startup crashes that I captured through Honor phone. I hope it can be helpful

Hi @pengyangjin - thanks for the log, but that doesn't start early enough - there's already an AIR process running when the logging starts. Looks like it's being switched into the background, it gets an onPause, and then is destroyed.

Are you able to ensure no tasks are running at all, then start the logcat logging, and then launch the application completely from scratch? What actually happens on the screen, do you see it appear and then disappear etc? (the video you originally uploaded doesn't seem to have made it onto github attachments..)

thanks

74df0b0bc020d8f75511b642ae5f9337.zip
This is the video I recorded.No more logs were captured.Sometimes it crashes one time, sometimes it crashes multiple times.

Thanks .. interesting one, it seems to be trying to switch orientation and then crashes as it does so. Do you have the 'background runtime' flag on? And would it be possible for us to get the installation APK so that we can try it here (and we can then swap out the official .so runtime file for a debug version, to try to dig into the details)? -> if so, I'll provide an upload link..

thanks

Thanks @pengyangjin - our IT restricts a lot of file-sharing sites so could you please upload to:
https://transfer.harman.com/requests/Q7vUoyiN2aEnzEdCnjo0SH
thanks

Is there any progress for this bug?

Hi @pengyangjin - apologies, I should have updated you - I tried installing the APK here, and it worked fine.. tried it with both auto-rotate on and off, I did wonder if it was to do with a rotation lock. Without auto-rotate, the start-up seems a little more like in the video, with a slight hesitation as the application opens. But I've not been able to make this crash..

Have you managed to confirm that it works fine with different SDKs? If you can pinpoint the point at which it changes, we can start looking at the differences between versions at that point?

thanks

Hi @pengyangjin - apologies, I should have updated you - I tried installing the APK here, and it worked fine.. tried it with both auto-rotate on and off, I did wonder if it was to do with a rotation lock. Without auto-rotate, the start-up seems a little more like in the video, with a slight hesitation as the application opens. But I've not been able to make this crash..

Have you managed to confirm that it works fine with different SDKs? If you can pinpoint the point at which it changes, we can start looking at the differences between versions at that point?

thanks

Everything is OK at AIR SDK 50.2.1.1 and earlier versions.The application locks the screen rotation. aspectRatio=landscape