Closed ekigamba closed 3 years ago
This is a bug and might mean memory leakage in production apps. It might also mean initialization being done multiple times on the Fragment
2021-01-21 13:10:36.353 6030-6103/org.smartregister.goldsmith D/EGL_emulation: eglMakeCurrent: 0xdf1a8d00: ver 2 0 (tinfo 0xe3e07c70) 2021-01-21 13:10:36.620 6030-6030/org.smartregister.goldsmith W/LocationUpdateReceiver: LocationEngineResult == null 2021-01-21 13:10:41.432 6030-6030/org.smartregister.goldsmith I/TaskRegisterFragment: LocationClient has stopped location udpates in #onPause 2021-01-21 13:10:41.433 6030-6030/org.smartregister.goldsmith I/TaskRegisterFragment: LocationClient has stopped location udpates in #onPause 2021-01-21 13:10:41.501 6030-6103/org.smartregister.goldsmith D/EGL_emulation: eglMakeCurrent: 0xdf1a8d00: ver 2 0 (tinfo 0xe3e07c70) 2021-01-21 13:10:43.857 6030-6030/org.smartregister.goldsmith I/TaskRegisterFragment: LocationClient has requested for location udpates in #onResume 2021-01-21 13:10:43.857 6030-6030/org.smartregister.goldsmith I/TaskRegisterFragment: LocationClient has requested for location udpates in #onResume
There were two Timber trees causing this to be logged twice
This is a bug and might mean memory leakage in production apps. It might also mean initialization being done multiple times on the Fragment