Ben Neill

We are seeing something similar, using 1.2.1 We have tried playing with memory and CPU as well, no difference.

We ended up finding the issue for us, our service accidentally got moved onto a bottlerocket host instance on AWS. Not sure on the details of why it caused problems...

Any chance of getting this merged @Norbert515 ?

I'm at the same point. I want to use the newer APIs but I have no way to reliably test this since the Shadow only seems to handle registration/deregistration testing....

oh right. so you can trigger the callbacks directly: ``` val networkType1 = ShadowNetwork.newInstance(1) val networkType2 = ShadowNetwork.newInstance(2) // connected for one network type shadowConnectivityManager.networkCallbacks.forEach { callback -> callback.onAvailable(networkType1) }...

I found declaring an anonymous function as default export directly caused this error, whereas assigning to a const and exporting that worked. e.g. doesn't work: ``` default export ({ path,...

@speedskater sorry, been on holidays. Will try and push something up when I get a chance (an remember what I was actually doing!).

We mostly moved to recyclerviews and treated the list as a flat list with different view types. when you expand, insert the items after the header item, when collapsed, remove...

Unfortunately not @ProfPh , I've moved on from that job so can't even access it now. From memory it shouldn't be hard to replicate: - single recyclerview - configure for...

The collapse/expand methods are in the wrapper adapter so it isn't easily accessible as far as I can see... I have forked and made an xml attribute for this, I...