Symptom
After disconnecting a session the Publisher continues to capture images from the camera and the camera indicator in the status bar continues to show.
Applies To
- Vonage Video API
- Android Client SDK
Resolution
If you require the publisher to stop on session disconnect you should use Session's onDisconnected() or Publisher's onStreamDestroyed() events to stop the publisher by calling:
mPublisher.onStop()
If you wish to re-use the publisher after calling this method you can use:
mPublisher.onRestart()
Cause
This behaviour is by design. It allows for more control over the captured video and audio streams. The Publisher and Session objects are separate entities.
Additional Information
You can find more information on these functions and attributes in the Android SDK documentation.
Also, our Developer Centre has additional resources and tutorials.
Vonage Video API Opentok Environment
Vonage Video API Unified Environment
Articles in this section
- How to use Completion handler for Exception Handling
- Firefox Pre-call test not supported
- Error Creating Session Using Vonage Video API .NET SDK
- Unable to Create Session Even Though API Key and Secret Are Valid
- HTTP 415 Error When Archiving Video Session
- Troubleshooting Invalid JWT When Creating a Video Session using REST API
- Camara Still in Use after Session Disconnect on Android
- Token Shows as Invalid
- HTTP 400 Error When Archiving Video Session
- 1541 Timed out while attempting to publish Error