Hi Nuno,
my customers are using Pixel and S25 without problems at startup.
What is your Qt version, Target API, and NDK version?

BTW: I noticed a Nullpointer at quitting some of my customer apps - but harmless—users don't notice anything. (Qt 6.10.2, Target API 36, NDK 27) Unfortunately not found a way to make it reproducable yet, but working on this. (Just transitioning all my apps to 6.10 and SafeArea-refactorings)
ciao
ekke
W/default : java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object android.content.Context.getSystemService(java.lang.String)' on a null object reference W/default :     at org.qtproject.qt.android.networkinformation.QtAndroidNetworkInformation.getConnectivityManager(QtAndroidNetworkInformation.java:158) W/default :     at org.qtproject.qt.android.networkinformation.QtAndroidNetworkInformation.unregisterReceiver(QtAndroidNetworkInformation.java:151) W/default :     at org.qtproject.qt.android.QtNative.startQtApplication(Native Method) W/default :     at org.qtproject.qt.android.QtNative$$ExternalSyntheticLambda5.run(D8$$SyntheticClass:0)
W/default :     at org.qtproject.qt.android.QtThread$1.run(QtThread.java:25)
W/default :     at java.lang.Thread.run(Thread.java:1563)

Am 24.03.26 um 20:07 schrieb Nuno Santos via Interest:
Hi,

I'm in the middle of a crash-elimination effort across my Android apps and I've 
hit a wall with a specific class of crashes I can't seem to own. They happen at 
app startup, before my code is reached, and show up most on high-end devices 
like Pixel and Samsung S25.

Stacktraces are always very similar (example below). My gut says it's something 
at the native/loader level but I'm not sure where to dig.

Anyone dealt with something like this? How did you track it down?

Thanks,

Nuno


           Crashed: Thread: SIGABRT  0x0000000000000000
#00 pc 0x7137c libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#01 pc 0x71354 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#02 pc 0x5d26c libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#03 pc 0x5dcbc libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#04 pc 0x5dc30 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#05 pc 0x5de18 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#06 pc 0x5f7d0 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#07 pc 0x119170 libandroid_runtime.so (BuildId: 
ce43a883b125c777ef749883d69eb39e)
#08 pc 0x72ab35d4
#09 pc 0x2ab6d4 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#10 pc 0x7286d480
#11 pc 0x7286d79c
#12 pc 0x72685d58
#13 pc 0x7286d924
#14 pc 0x7286cf90
#15 pc 0xc0f07c libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#16 pc 0x726215f0
#17 pc 0xc0dffc libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#18 pc 0x2aaf94 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#19 pc 0x2708ec libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#20 pc 0xc0d3bc libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#21 pc 0x4bdfe0 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#22 pc 0xc0dffc libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#23 pc 0x4bdb30 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
#24 pc 0x10bffc libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#25 pc 0x82740 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#26 pc 0x74b98 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#27 pc 0x82684 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
#28 pc 0x18d094 ld-android.so (BuildId: 44249f662570b6c2670db1a98725cc14)
#29 pc 0x18d394 ld-android.so (BuildId: 44249f662570b6c2670db1a98725cc14)
#30 pc 0x4bdb24 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
_______________________________________________
Interest mailing list
[email protected]
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
[email protected]
https://lists.qt-project.org/listinfo/interest

Reply via email to