App crash on open after inactivity
Wally iOS crashed as soon as I opened the phone in the morning
if I had to make a wild guess, libnexakotlin creates a new thread to shepard a connection through the "hello" process... the system only tries a few new connections at a time. But I'll bet this is somehow "running away"
From the (extensive) crash logs:
3 src 0x103a34c34 kfun:org.nexa.threads.iGate#timedwaitfor(kotlin.Long;kotlin.Function0<kotlin.Boolean>;kotlin.Function0<0:0>){0§<kotlin.Any?>}0:0?-trampoline + 204
4 src 0x103327bb0 kfun:org.nexa.threads.iGate#delayuntil(kotlin.Long;kotlin.Function0<kotlin.Boolean>){}kotlin.Boolean + 128
5 src 0x1038fed2c kfun:info.bitcoinunlimited.www.wally.AssetLoaderThread$lambda$4#internal + 472
6 src 0x1038ff110 kfun:info.bitcoinunlimited.www.wally.$AssetLoaderThread$lambda$4$FUNCTION_REFERENCE$0.invoke#internal + 24
7 src 0x1038ff130 kfun:info.bitcoinunlimited.www.wally.$AssetLoaderThread$lambda$4$FUNCTION_REFERENCE$0.$<bridge-UNN>invoke(){}
This indicates that the crash is related to asset loading. ctrl+f "socket" = no results
Edited by Jørgen Svennevik Notland