Closed shawafoncoustics closed 1 year ago
Thanks for reporting I will investigate.
Hi @shawafoncoustics no news for now. I was not able to exactly replicate your crash--I was able to cause a crash each time following your workflow (start app > ble screen > select ble info > auto-join > connect > load probe/application > disconnect > ble screen, which causes solum resources deletion > select ble info, which causes solum resources creation > auto-join > connect > load probe/application, which causes the crash). However my error is slightly different:
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x00000072ab987ca4
Notice the SEGV_ACCERR
while yours is SEGV_MAPERR
. I will continue investigating.
Workaround: avoid destroying/recreating the solum object repeatedly, for example by placing it in a service (outside the fragment which gets created/deleted when changing view). Production code should probably avoid tying the lifetime of the solum object with that of a view (the example app does it to help detect bugs, like the one you found, thanks again for reporting).
@shawafoncoustics would you be able to send the logcat output to me? Be sure to remove any patient health information. You can attach it to this ticket or send it to me via email. Thanks!
Hi @julien-l i sent u the full locat output on mail, thanks.
Describe the bug Solum v10.3, v10.4 beta throws an error and causes the app to crash when trying to load the workflow on Android version, the workflow works for the first time with no problem but when we do reset it like following
and try to connect again we got this error and the app crash
To Reproduce Steps to reproduce the behavior:
Environment:
Note: By using exact same setup and workflow, this issue wasn't happening with the previous version 10.2.