distriqt / ANE-IronSource

IronSource ANE updated to latest SDK
5 stars 0 forks source link

crash on latest ane with adapters #33

Closed bobrokrol closed 2 years ago

bobrokrol commented 2 years ago

air sdk: . . 821 target api level: 30

 #00  pc 0x00000000004e152c  /apex/com.android.runtime/lib64/libart.so (art::CodeInfo::CodeInfo(art::OatQuickMethodHeader const*, art::CodeInfo::DecodeFlags))
  #00  pc 0x000000000045d990  /apex/com.android.runtime/lib64/libart.so (art::OatQuickMethodHeader::ToDexPc(art::ArtMethod*, unsigned long, bool) const)
  #00  pc 0x00000000001f031c  /apex/com.android.runtime/lib64/libart.so (art::FaultManager::IsInGeneratedCode(siginfo*, void*, bool))
  #00  pc 0x00000000001efc60  /apex/com.android.runtime/lib64/libart.so (art::FaultManager::HandleFault(int, siginfo*, void*))
  #00  pc 0x0000000000004ecc  /system/bin/app_process64 (art::SignalChain::Handler(int, siginfo*, void*))
  #00  pc 0x000000000000063c  [vdso] (__kernel_rt_sigreturn)
  #00  pc 0x00000000005a2c5c  /apex/com.android.runtime/lib64/libart.so (MterpInvokeInterface)
  #00  pc 0x0000000000131a14  /apex/com.android.runtime/lib64/libart.so (mterp_op_invoke_interface)
  #00  pc 0x00000000009b1b38  /data/app/air.hetsoft.tunerv2-L2FsnhCgRT9f7CcMdx6uWw==/oat/arm64/base.vdex (com.facebook.ads.internal.dynamicloading.DynamicLoaderFactory.doCallInitialize)
  #00  pc 0x00000000005a7318  /apex/com.android.runtime/lib64/libart.so (MterpInvokeStaticRange)
  #00  pc 0x0000000000131c94  /apex/com.android.runtime/lib64/libart.so (mterp_op_invoke_static_range)
  #00  pc 0x00000000009b1ad0  /data/app/air.myappID-L2FsnhCgRT9f7CcMdx6uWw==/oat/arm64/base.vdex (com.facebook.ads.internal.dynamicloading.DynamicLoaderFactory.access$200)
  #00  pc 0x00000000005a7318  /apex/com.android.runtime/lib64/libart.so (MterpInvokeStaticRange)
  #00  pc 0x0000000000131c94  /apex/com.android.runtime/lib64/libart.so (mterp_op_invoke_static_range)
  #00  pc 0x00000000009b12a4  /data/app/air. myappID-L2FsnhCgRT9f7CcMdx6uWw==/oat/arm64/base.vdex (com.facebook.ads.internal.dynamicloading.DynamicLoaderFactory$1.run)
  #00  pc 0x00000000002b4b14  /apex/com.android.runtime/lib64/libart.so (art::interpreter::Execute(art::Thread*, art::CodeItemDataAccessor const&, art::ShadowFrame&, art::JValue, bool, bool) (.llvm.3344685479926618679))
  #00  pc 0x0000000000592d18  /apex/com.android.runtime/lib64/libart.so (artQuickToInterpreterBridge)
  #00  pc 0x0000000000140468  /apex/com.android.runtime/lib64/libart.so (art_quick_to_interpreter_bridge)
  #00  pc 0x00000000004afbd8  /system/framework/arm64/boot.oat (java.lang.Thread.run)
  #00  pc 0x0000000000137334  /apex/com.android.runtime/lib64/libart.so (art_quick_invoke_stub)
  #00  pc 0x0000000000145fec  /apex/com.android.runtime/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*))
  #00  pc 0x00000000004b171c  /apex/com.android.runtime/lib64/libart.so (art::(anonymous namespace)::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art::(anonymous namespace)::ArgArray*, art::JValue*, char const*))
  #00  pc 0x00000000004b2830  /apex/com.android.runtime/lib64/libart.so (art::InvokeVirtualOrInterfaceWithJValues(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, jvalue const*))
  #00  pc 0x00000000004f31ec  /apex/com.android.runtime/lib64/libart.so (art::Thread::CreateCallback(void*))
  #00  pc 0x00000000000e6a10  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*))
  #00  pc 0x0000000000084c6c  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread)

It happens to different users according to play console and currently it is most common crash

marchbold commented 2 years ago

Have you correctly packaged the audience_network.dex in your application?

bobrokrol commented 2 years ago

Have you correctly packaged the audience_network.dex in your application?

facebook ads works on my devices. Its crash Log from play console. But

I am using audience_network dex from Adverts repo as original from ironsource repo didnt work. They seems to be different and I had issues with dex from this repo. Also it seems to be placed in the assets folder instead of assets/android . I have packaged dex file from Adverts repo directly into assets folder and I see both banner and full screen ads from facebook. I will write more details if similar crash happens. In general Ironsource + adapters crashes much more than Adverts + adapters

marchbold commented 2 years ago

No not in an assets folder. It must be at the root level of your AIR application, all AIR content at the root level will be packaged into Android's assets directory, so don't include an assets directory in your AIR content otherwise it will get packaged into assets/assets on Android.

With apm everything in the assets/android folder must be added at the root level of your android application, same applies to assets/ios for iOS applications.

ironsource and admob may use different versions of the audience network sdk so you must include the one from the advertising network you are using.

bobrokrol commented 2 years ago

No not in an assets folder. It must be at the root level of your AIR application, all AIR content at the root level will be packaged into Android's assets directory, so don't include an assets directory in your AIR content otherwise it will get packaged into assets/assets on Android.

With apm everything in the assets/android folder must be added at the root level of your android application, same applies to assets/ios for iOS applications.

ironsource and admob may use different versions of the audience network sdk so you must include the one from the advertising network you are using.

apm? assets/android? Everything I need to make a package is adt and Im using it to make a bundle. By assets I meant the root assets folder of Android package where swf located What does mean assets/android?

Yes dex files are different and dex from latest ironsource release seems not working as expected.

May be theese crashes was caused by misplaced dex file, as I did numerous of other releases I need to take a look if it happens again. Anyvay I have never had issues on testing devices

marchbold commented 2 years ago

Apologies, I misread the comment and thought you were using apm. I was confused by your reference to assets/android which is what apm provides for platform specific content.

Sounds like you are packaging it correctly, yes the root swf is packaged in the assets folder on Android and this is where the audience network dex file must be located.

We have a new release of this mediator coming out this week so perhaps try that when it comes out to see if it is an issue with the dex file.

marchbold commented 2 years ago

I've just pushed the update out, let me know if you still have issues.

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 2 years ago

This issue was closed because it has been stalled for 5 days with no activity.