> If after bindService, there is an orientation change or the activity is > finished before onServiceConnected is called, myBinder will still be > null, and your code won't call unbindService, despite having called > bindService.
You're right, I'll change that. > Don't know if this can later cause the exception you're describing, I don't think so. The exception should occur when unbindService is invoked without a previous bindService. But in the case you described, it would be the other way around: bindService would've been invoked multiple before unbindService is invoked. That might be bad because a bound service isn't destroyed, but shouldn't cause this exception. (Btw: How is it with multiple bindService to the same ServiceConnection object? Does Android detect it's the same connection, or is an unbindService necessary for each bindService?) -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
