I'm using AVAssetWriter, and it is perfectly working on iOS6.
The problem is, when I called finishWritingWithCompletionHandler
, the completion handler is not called on iOS7 GM.
I called markAsFinished
, and even endSessionAtSourceTime
before I call finishWritingWithCompletionHandler.
It works fine on iOS6.
And even more, on iOS7, it works some times, and then it doesn't work again.
I don't know why, but it works if I call the method using alert view.
So I tried performSelectorOnMainThread
and inBackground
, but it didn't help.
Any ideas?
This happen on ARC as well.
The simplest solution is to define properties of AVAssetWriter(and AVAssetReader I assume)
and then
and in the completion block
It also can happen if destination directory does not exist. In this case writing works fine, but no file created and the block is not called.
Ray Fix, you are right. We need to retain assetWriter. The easiest way is to use it inside the finishWritingWithCompletionHandler block:
Apparently you need to retain the assetWriter now.
You might try retaining with a strong property it and see if your completion handler gets called. (Be sure to nil that property in completion handler.)
Retaining the assetwriter is very important but I also ran into a very strange intermittent failure even though my assetwriters were all retained (and never reused). The problem also wasn't a file name collision or missing directory because my file names are all based on CACurrentMediaTime() and don't change directories.
It seems if you don't set
endSessionAtSourceTime:
for the assetwriter every time, there's a very rare (but reproducible) chance the completion handler forfinishWritingWithCompletionHandler:
won't ever be called. If you wait a few seconds and check on the status of the assetwriter, it will be in the AVAssetWriterStatusFailure state and the error will be a non-descript "An unknown error occurred (-12763)". Additionally, changing the file format for the assetwriter doesn't see to have an effect on this problem. Lastly, this problem is probably only an issue if you need to rapidly record movies over and over again (as the chance for failure is probably 1/15 - 1/20).So, just be sure to store the presentation time stamp for the last sample you're passing to the assetwriter and to call
endSessionAtSourceTime:
with that sample time right before you're about to callfinishWritingWithCompletionHandler:
.