The MediaSessionService never destroyed When I Open App I can see Old Data.

[DolaKrishnan08]

The MediaSessionService never destroyed When I Open App I can see Old Data.

[marcbaechinger]

You start the MediaSessionService by building a MediaController that then binds to the service.

The documentation section about the Service lifecycle explains how to stop the service.

[DolaKrishnan08]

Hello @marcbaechinger

1. In My App I'm not using MediaController so I think this won't bind to the Service.
2. As Document Suggested I'm clearing all instance when onDestroy is Triggered

fun stopService() {
            mediaSession.run {
                player.stop()
                player.release()
                release()
            }
            stopSelf()
    }
    override fun onDestroy() {
        stopForeGround()
        hideNotification()
        super.onDestroy()
    }
    
    private fun stopForeGround() {
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {
            stopForeground(STOP_FOREGROUND_REMOVE)
        } else {
            stopForeground(true)
        }
    }
    fun hideNotification() {
        playerNotificationManager?.setPlayer(null)
        playerNotificationManager= null
    }

[marcbaechinger]

The intended use of MediaSessionService is to be started with a controller and to use the controller to control playback. If based on your experience you choose to do your own thing this is fine, but I don't think we can extensively support you with this endeavor I'm afraid.

I'd recommend using the MediaSessionService with a controller. But surely, that decisions is yours.

The MediaSessionService implementation aims to make things easier for users that don't want to build their own service and hence don't need to read through the extensive foreground service documentation. Users that want to/have to read this documentation find that stopSelf is a no-op in the case the service is still running in the foreground. So you'd have to call stopForeGround() before calling stopSelf()?

When not requiring a controller, I think I'd just create my own Service implementation and refrain from using MediaSessionService. This may be easier than bending MediaSessionService your way. Certainly we are convinced that using MediaSessionService in the intended way is the easiest approach and benefits developers that want to build a media app.

[DolaKrishnan08]

Hello @marcbaechinger
I Got Your Point It's Best to use MediaController when the service is MediaSessionService may be I will looks in to this, But Once MediaSessionService is Started as Normal Service with startForeGroundService(ServiceName) In OnStartCommand I am pushing PlayerNotificationManager with startForeground(NotificationConstants.NOTIFICATION_ID, notification)

Once User is Closing the App From OnDestroy I'm calling StopService(Service) where I Clear All Instance and stopForegound like private fun stopForeGround() {
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {
stopForeground(STOP_FOREGROUND_REMOVE)
} else {
stopForeground(true)
}
}

After This I'm calling **stopSelf()** Notification was cleared But Service is Not Destroying Any Suggestions on This Would Help me lot, Thank You!!