New upgrade 0.7.2 crashing constantly

[tommy2809]

• Uploader Version Number: v0.7.2

• Your Android Phone Model Name (e.g. Samsung J1 Ace): Samsung S7 Edge and Fire 7 (7th Gen)

• Android Version Number (e.g. use 4.4 for 4.4.4): 8.0 (SamsungS7 Edge)

• Network Connection at the time the issue occurred (Wi-Fi, Mobile): Wi-Fi mainly

• Nightscout website version (e.g. 0.8.4 Funnel cake, master / dev branch): v14.0.6 / head

Brief Explanation of Issue

After updating to 0.7.2 yesterday, The uploader app has crashed on numerous occasions. I have tried on both uploaders; Samsung S7 Edge and on the Fire 7 (7th Gen) tablet and it has been happening constantly throughout the night and this morning. I would be grateful for any help. Thanks

Severity Score 4

[rikstewart]

I'm getting the same. Pretty sure our uploader is a Samsung Galaxy S7.

Been 100% brilliant up until the app updated yesterday. Hope this is sorted soon.

Thank you for the great work as this is literally a life saver. 👍

[tommy2809]

I'm getting the same. Pretty sure our uploaded is a Samsung Galaxy S7.

Been 100% brilliant up until the app updated yesterday. Hope this is sorted soon.

Thank you for the great work as this is literally a life saver. 👍

Hi, I just uninstalled it and rolled back to 0.7.1 for now,but only done this on one of my uploaders for the moment but at least I am back up and running.You will have to make sure you have all your settings before you rollback.

[rikstewart]

Thanks Tommy. Have you had a crash since rolling back to 0.7.1?

When did you upgrade to v14 of Nightscout? I see you are on 14.0.6. I updated to 14.0.7 recently. I thought important to mention.

[tommy2809]

No problem Rik, it has been working perfectly since I done the rollback. Only noticed that 14.0.7 Nightscout was out today so must do that soon but just happy to be back up and running. Thanks for sharing the info with me though. Hopefully you get back up and running again soon after rolling back.

[rikstewart]

Roll back got us back to functioning. Thank you.

[pazaan]

Apologies for the hassle with 0.7.2. It was a one line code change (and only a text label at that), but I needed to update a bunch of dependencies to get it to build. I'll have a look through the crash logs and see what's causing this problem.

[tommy2809]

Thanks Pazaan,no need to apologise,we are very grateful for your help and we would be lost without it.

[Pogman]

Hi - can you guys try the 0.7.3 version and see how it goes for you?

[rikstewart]

It’s not coming up with an update when I click “check for app updates” in 0.7.1. Not sure why.

[rikstewart]

I deleted and installed 0.7.3. First time it kept all my settings but crashed. Thought I’d done something wrong so deleted and installed again. It has crashed since again crashed. The crash is closing down the app silently each time.

[Pogman]

@rikstewart your using a Samsung Galaxy S7 ? The uploader crash reporter service does not seem to have a note related to that device making this very difficult to isolate.

I do see a crash for a "Samsung Galaxy Tab 3 10.1" and that's it... mmm will have a think.

[rikstewart]

This is what I should have written, I think, earlier.

Uploader: 0.7.3 Brand: Samsung Device: herolte ID: R16NW Hardware: samsungexynos8890 Manufacturer: samsung Model: SM-G930F Product heroltexx SDK: 26 Version 8.0.0

Hope this helps.

[tommy2809]

Hi, I done the update to 0.7.3 and I am getting the same,where the app closes itself for no reason.It doesn't present an error and seems to still read but the app keeps closing for no apparent reason.I was using a Fire 7 tablet as the uploader when this happened.Let me know if you need anymore info.Thanks.

[rikstewart]

Was no point in sending it to school with my daughter, so have had it running next to me. I turned off Pushover to avoid alert hell. No crashes yet. Pushover could be coincidence as it may be something to do with not having the pump near. I'm just about to turn pushover back on. I'll give it a couple of hours and report back.

[rikstewart]

[rikstewart]

Could be coincidence, but don’t appear to have an issue when pushover deactivated.

[Pogman]

@rikstewart this could be an issue with pushover will have a look

[Pogman]

I was able to trigger this crash with pushover use but there is no actual problem with the code. I changed things around and stopped the crash but something else odd and unrelated crashed hours later. The crashes are similar and seem to related to the many updated support libraries using on android.

So this is still unresolved but investigating.

[rikstewart]

Thank you. After sustained periods sat with the pump and with Pushover activated/deactivated, I can conclude/concur for me this is Pushover but sadly I can't see a reason or particular status as to what is leading up to the crash. Good luck investigating. 👍

[pazaan]

I wonder if it's the Toast crashes...

[Pogman]

It's a super hard hard crash that takes all parts of the process down including the firebase crash reporter.

2020-11-24 13:55:01.869 A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x740074 in tid 18239 (Thread-16), pid 18108 (htscout.android)

Indicates memory corruption.

This is a Realm DB issue and with something that worked for years but was probably an unsafe way of doing certain things and the latest version is biting back. Surprised there wasn't a proper java exception though.

Anyhow I think I have a fix for it.

[rikstewart]

Sorry I'm a bit new to Github. Is there a way to update to the version that has the fix so I can feed back if it works? TIA

[Pogman]

This issue is still being investigated but dev time has been very limited. There are still issues related to this bug. Stick with 0.7.1 for the time being.