爲什麼unregisterReceiver（）永遠不會調用onServiceDisconnected？

Question

我綁定到一個服務在我的活動：

override fun onStart() { 
    Timber.d("onStart") 
    super.onStart() 
    val intent = Intent(this, MyService::class.java) 
    bindService(intent, serviceConnection, Context.BIND_AUTO_CREATE) 
} 

迄今工作。然後bindService()電話onServiceConnected()：

/** Defines callbacks for service binding, passed to bindService() */ 
private val serviceConnection = object : ServiceConnection { 

    override fun onServiceConnected(className: ComponentName, 
            service: IBinder) { 
     // We've bound to MyService, cast the IBinder and get MyService instance 
     val binder = service as MyService.MyBinder 
     myService = binder.service 
     isBound = true 
     registerReceiver(myBroadcastReceiver, filter) 
    } 

    override fun onServiceDisconnected(arg0: ComponentName) { 
     myService!!.removeRecevier(this@MainActivity) 
     isBound = false 
     unregisterReceiver(myBroadcastReceiver) 
    } 
} 

在我onStop()我也有unbindService(serviceConnection)，但這裏的onServiceDisconnected（）永遠不會觸發？ 我在做什麼錯？

所以我得到：

Activity MainActivity has leaked IntentReceiver com.example.MyBroadcastReceiver@68091a2 that was originally registered here. Are you missing a call to unregisterReceiver()? 
 
android.app.IntentReceiverLeaked: Activity MainActivity has leaked IntentReceiver com.example.MyBroadcastReceiver@68091a2 that was originally registered here. Are you missing a call to unregisterReceiver()?

Answer 1

你誤會時的服務連接已丟失叫的onServiceDisconnected()

目的。這通常發生在承載服務的進程崩潰或被殺死時。這不會刪除ServiceConnection本身 - 與服務的綁定將保持活動狀態，並且在下次運行服務時您將收到對onServiceConnected(ComponentName, IBinder)的呼叫。

所以這實際上只有在你斷開與實際服務的連接時才被調用。當您從服務中解除綁定時，您必須手動進行清理。更好地處理與ServiceConnection不同（其他）級別的接收器 - 例如onStart()/onStop()。