Ошибка 5825 при записи экрана

RaymondRaymond

1,10513 silver badges32 bronze badges

Have you tried to set AVAudioSession category to .multiRoute or .playAndRecord?

do {
    let session = AVAudioSession.sharedInstance()
    try session.setCategory(.multiRoute)
    try session.setMode(.default /* or .moviePlayback*/)
    try session.setActive(true, options: options)
} catch {
    print("ActiveAudioSession failed.")
}

I have the same issue but can’t always reproduce it, so my next try is to add this lines of code.

Another thing I found here — https://discussions.apple.com/thread/251342404

which says:

That usually appears when there is a space issue. Do you have ample free space on the iPhone? How long of a screen recording was it? Did you attempt to record any copyrighted materials?

UPDATE
seems to be it could be also a bug in iOS 14+

My app includes video streaming, but I’m experiencing peculiar problems specifically in
screen recording
on iPhone. One noticeable problem is that when live streaming,
screen record
, the iPhone cannot save
recorded screen
and displays an error message with code 5825.

My app faces the problem of audio halting when I begin the screen recording. However, I am able to record other apps like YouTube without any issues.

There is a suggestion that the issue may be related to insufficient storage, but I have ample space on all of my devices. Despite testing the problem on multiple iPhones, the same issue persists.

I am curious if there are any specific requirements or precautions that need to be taken within my app to enable screen recording.

Is the problem with my app (code) or is it solely related to the device?

Have you attempted to assign the

AVAudioSession

classification to either

.multiRoute

or

.playAndRecord

?

do {
    let session = AVAudioSession.sharedInstance()
    try session.setCategory(.multiRoute)
    try session.setMode(.default /* or .moviePlayback*/)
    try session.setActive(true, options: options)
} catch {
    print("ActiveAudioSession failed.")
}

Although I face a similar problem, I am not always able to replicate it. Hence, my plan is to append these lines of code in my next attempt.

I discovered something else on the following page — https://discussions.apple.com/thread/251342404.

which says:

The appearance of this issue is usually linked to a lack of space. You should check if your iPhone has enough free space. Additionally, you may want to consider the length of the screen recording and whether you recorded any copyrighted materials.

It appears that there may be a potential bug in iOS 14+ that requires attention.

After conducting a session with my father, I saved the recording to my Desktop and opened the file by clicking the icon that appeared on the lower right corner. To ensure the recording was functional, I played back a few minutes of it.

Following my unsuccessful attempt to share the file via AirDrop to my computer, I cancelled the process as the status remained «cancelled». Hoping to access it through my phone, I planned to send it via a third-party app and clicked cancel on the AirDrop pop-up window.

Following the action, the complete screen recording shut down and (seemingly) disappeared permanently. My inability to locate this video has left me feeling highly frustrated.

It would have been more convenient to take a picture of capturing an image, but unfortunately, Apple does not permit it.

To record the monitor or
portion of the screen
, you can use the key sequence for Screenshot and recording options located in System Preferences > Keyboard > Screenshots. Then, you can choose where to save the recording from options such as Desktop,
Documents, Clipboard
, Mail, Messages, Preview, and Other Location. It’s unclear how you changed the destination between your first recording, which was likely saved to the clipboard, and the second, which was saved to the Desktop.

Please use regedit to rename hklm\software\policies\microsoft\windows\
AppCompat — change


AppCompat


to


AppCompat_HOLD


.

Arnav Sharma, whose website is arnavsharma.net, suggests marking a helpful post as the answer, and unmarking it if it doesn’t answer your question. This will benefit other members of the community who read the thread.

Hi,

Can you please specify the error message you received? Or is there no response when you click the «stop» option? Additionally, could you provide information about the updates that were installed?

To address the issue, I recommend running Problem
Steps Recorder
as an administrator before proceeding.

In case the issue persists, it could be related to the Problem Steps Recorder identified as
files corruption
. To troubleshoot this, you can use Process Monitor to gather information on the packages associated with the Problem Steps Recorder and locate its source files. Once located, you can copy the new files from a functional computer to the problematic one, marked as
issued PC
.

Refer to the Microsoft TechNet website at the following URL for more information:
https://technet.microsoft.com/en-us/library/bb896645.aspx

One possible solution is to use System Restore to revert your PC to a previous point in time before the updates were installed. This may help resolve the issue you are experiencing.

Visit the Windows website to learn about the purpose and functionality of System Restore.

I hope you are able to resolve the issue successfully.

Best Regards

Simon

Kindly ensure that you mark the responses that assist you as answers, and deselect the ones that do not. In case you have any feedback for TechNet Support, you can reach out to them at tnmff@microsoft.com.