Uploading the recorded files to the cloud storage fails if:
acquiremethod to get the recording resource, you set the
uidparameter that matches that of a user ID already in the channel. For example, suppose three users are in the channel with user IDs as
345. If you set
123when calling the
acquiremethod, the recording fails.
startmethod do not follow the recommended settings, which causes the recording to fail. See How do I set the video profile of the recorded video? before setting
The URL of the M3U8 file consists of the domain of your cloud storage and the filename. You can copy the URL in your cloud storage.
You can get the filename of the M3U8 file from the following fileds:
fileListfield in the responses of
fileListfield in the
You can call the
stop method to leave the channel and stop recording.
Agora Cloud Recording automatically stops recording and leaves the channel when there is no user in the recording channel after a time period (30 seconds by default). You can set this timeout interval by the
maxIdleTime parameter when you start the recording.
"ErrorUint32":101 error in the log file is usually caused by a token error, such as in the following situations:
The recording exits abnormally when the app crashes. As long as the call or live broadcast is ongoing, the Agora Cloud Recording service keeps recording and uploading. You can use the original App ID, channel name, and UID to join the channel again and take control of the original recording instance.
A Web API needs to make a cross-origin request in accordance with Cross-Origin Resource Sharing (CORS) to call the Cloud Recording RESTful API. The browser must first send an OPTIONS request to the server to query if the server accepts cross-origin requests before sending a cross-origin POST request. However, the Cloud Recording RESTful API does not support the OPTIONS method, and therefore you cannot call it with a Web API.