Unity-Technologies / com.unity.mobile.notifications

Mobile Notifications Package
https://docs.unity3d.com/Packages/com.unity.mobile.notifications@2.1/manual/index.html
Other
131 stars 42 forks source link

Native method - android.os.MessageQueue.nativePollOnce Broadcast of Intent { cmp=linkdesks.pop.bubblegames.bubbleshooter/com.unity.androidnotifications.UnityNotificationManager } #252

Closed mry-ship closed 1 year ago

mry-ship commented 1 year ago

00 pc 0x00000000002fe297 /apex/com.android.runtime/lib/libart.so (art::DumpNativeStack(std::__1::basic_ostream<char, std::__1::char_traits>&, int, BacktraceMap, char const, art::ArtMethod, void, bool)+78)

01 pc 0x00000000003a6bdb /apex/com.android.runtime/lib/libart.so (art::Thread::DumpStack(std::__1::basic_ostream<char, std::__1::char_traits>&, bool, BacktraceMap*, bool) const+358)

02 pc 0x00000000003a33b3 /apex/com.android.runtime/lib/libart.so (art::Thread::Dump(std::__1::basic_ostream<char, std::__1::char_traits>&, bool, BacktraceMap*, bool) const+34)

03 pc 0x00000000003bbc2d /apex/com.android.runtime/lib/libart.so (art::DumpCheckpoint::Run(art::Thread*)+576)

04 pc 0x00000000003b65dd /apex/com.android.runtime/lib/libart.so (art::ThreadList::RunCheckpoint(art::Closure, art::Closure)+296)

05 pc 0x00000000003b5cfd /apex/com.android.runtime/lib/libart.so (art::ThreadList::Dump(std::__1::basic_ostream<char, std::__1::char_traits>&, bool)+1416)

06 pc 0x00000000003b5691 /apex/com.android.runtime/lib/libart.so (art::ThreadList::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits>&)+640)

07 pc 0x000000000038033b /apex/com.android.runtime/lib/libart.so (art::Runtime::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits>&)+130)

08 pc 0x000000000038ecad /apex/com.android.runtime/lib/libart.so (art::SignalCatcher::HandleSigQuit()+1036)

09 pc 0x000000000038e117 /apex/com.android.runtime/lib/libart.so (art::SignalCatcher::Run(void*)+242)

10 pc 0x00000000000a6293 /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+20)

11 pc 0x0000000000060803 /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30)

00 pc 0x000000000005a850 /apex/com.android.runtime/lib/bionic/libc.so (syscall+28)

01 pc 0x00000000000e44e5 /apex/com.android.runtime/lib/libart.so (art::ConditionVariable::WaitHoldingLocks(art::Thread*)+80)

02 pc 0x0000000000416db1 /apex/com.android.runtime/lib/libart.so (art::GoToRunnable(art::Thread*) (.llvm.14151189754156541143)+324)

03 pc 0x0000000000416c45 /apex/com.android.runtime/lib/libart.so (art::JniMethodEnd(unsigned int, art::Thread*)+8)

at android.os.MessageQueue.nativePollOnce (Native method) at android.os.MessageQueue.next (MessageQueue.java:336) at android.os.Looper.loop (Looper.java:182) at android.app.ActivityThread.main (ActivityThread.java:7563) at java.lang.reflect.Method.invoke (Native method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:539) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:994)

mry-ship commented 1 year ago

image

aurimasc commented 1 year ago

Could you tell, which Unity version (exactly) you use?

bw-atif commented 1 year ago

We are having the same ANR with the latest unity mobile notifications v2.1.0 and unity v2021.3.16f1.

cameronnotdoppler commented 1 year ago

We have the same issue Unity versions 2020.3.30f and 2021.3.16f Plugin version 2.1.0

KarahanOnarlar commented 1 year ago

We also have the same problem. For us, 99% of ANRs happen on android 10 and in the background. Unity version 2020.3.40f Plugin versions 2.1.0 and 2.1.1

aurimasc commented 1 year ago

Do you have stacktraces from Unity when it happens? I believe the answer is in there, rather than the one provided in this report.

aurimasc commented 1 year ago

The nativePollOnce errors occurs, when app recovers from non-responding before the OS managed to collect the data. Ignore these and look into other ANRs. The problem is real, but the data is in other ones. There is a delay between ANR detection and action, sometimes app gets responding in that window, so it's still killed as non-responsive, but the collected data no longer can show the reason. Usually there will be cases where app did not recover in time and those will have proper data to analyze.