髙沢
髙沢
Thank you for your reply. > Can you just check the output of the ANE using the Windows version of lipo please? I checked it with the windows version 33.1.1.889....
I've tried it with the new 33.1.1.889 and it still has this problem.
Hi @ajwfrost, thanks for answering my query. First I am wondering if some sort of threshold regarding PushLocalFrame and out-of-memory has changed between AIR SDK 33.1.1.575 and 33.1.1.856(889)? Or could...
Hi @ajwfrost I built with the two Runtime.apk's I received. First, here are the logs as of the 07/22 14:45 version. - [logcat_NG_kura_33.1.1.889_GalaxyS8_DebugRuntime.txt](https://github.com/airsdk/Adobe-Runtime-Support/files/9177348/logcat_NG_kura_33.1.1.889_GalaxyS8_DebugRuntime.txt) Next is the log as of 07/22...
I have a lot of meetings today and have not been able to work on it. I will check the operation right after this.
@ajwfrost I have launched the app several times with the new runtime build and nothing seems to be wrong. Looking forward to the new SDK release! - [logcat_OK_kura_33.1.1.889_GalaxyS8_DebugRuntime_03.txt](https://github.com/airsdk/Adobe-Runtime-Support/files/9180754/logcat_OK_kura_33.1.1.889_GalaxyS8_DebugRuntime_03.txt)
We are also working on this issue. In our case, Apple stopped saying anything by including a manifest that set the following four items as pointed out in the email...
@ajwfrost I don't know if this problem is a problem with the way we create ANE or with AIR. Could you please let me know if you have any clues?