Closed lukeswitz closed 6 years ago
Reason for explicit call: ensure the fragment is on the main thread to avoid conflict/confusion with the bind handler.
“when code is running inside onCreate(), onStartCommand(), or onDestroy(), it’s treated as if it was in foreground even if it’s not.”
Looking into the further ramifications of this; closing as it’s no one-line fix.
As @zhanglihow suggested, this fix works. Tested 5.1-6.0