Just once.
@britzl any decision here?
I forked ironsource ext
Also for comfort using divided into several exts with ironsource adapters
After release we got ANR Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x58200010 }
Last week ANR stats for this issue:
Any decision on what specifically?
Makes a lot of sense!
ANRs are notoriously hard to avoid completely. Can these ANRs be directly traced to the extension? At a specific time when using the extension?
Decision on this ANR, possible ways of emmerging?
No other minor changes were made, this is the only new native extention and ANR’s appeared after new release, can’t reproduse on my devices.
An ANR, as you know, means that something is blocking the UI/main thread for too long. We’ve seen numerous ANRs caused by various ad integrations, analytics services etc. It is very likely that this is caused by something in IronSource or one of the adapters.
We have not made any changes to the Android runtime, BUT we have migrated from the old deprecated DX dex tool to the new D8 tool. This will have an impact on how the APK is constructed and it could potential explain why you are seeing a problem now and not before. You can verify this by testing with 1.2.184 which was the release prior to the move to D8.
2 Likes