After having received the key server the video doesn't start

You should verify your key server can properly package the content key into a content key response. Use the CKC Verification tool and the pre-generated SPC and CKC test vectors in the FairPlay Streaming Server SDK to help debug these kinds of issues. See the section titled "Testing the Key Security Module" in the FPS Programming Guide for more information.

Thank you ,

We managed to play the video once and only on ios7.

After that " observeValueForKeyPath : ofObject : change: context" is recalled , we must change the bundle identifier.

It's normal?

I adding to my last post :

on ios 8 and 9 the function " observeValueForKeyPath : ofObject : change: context" is called after a long time >1min, the sames as it happend with ios7.

[self.player play];

It was called but on ios 8 and 9 the video isn't visible , and there haven't been the sound of the video.

do you have getten the same experience with the player as above? what is the mimimu version of iOS that will gerantee the Fairplay implemtation?

This would appear to be a content authoring issue or .m3u8 playlist issue. For debugging purposes only, to determine if it is a content authoring issue we recommend you set your EXT-X-KEY tag KEYFORMAT attribute in the .m3u8 playlist to "identity" instead of "com.apple.streamingkeydelivery", add the initialization vector (IV) of the key you are using to the IV attribute, and set the URI attribute to an http URL pointing to a (16-byte) resource containing only the raw, unencrypted AES key. For example, instead of something like this:

#EXT-X-KEY:METHOD=SAMPLE-AES,URI="skd://key67",KEYFORMAT="com.apple.streamingkeydelivery",KEYFORMATVERSIONS="1"

do something like this:

#EXT-X-KEY:METHOD=SAMPLE-AES,URI="http://mysite.com/my16ByteKey.bin",KEYFORMAT="identity",IV=0xA30FE123ECBF1BE323A775A119C553BC

and make your 16-byte key available on your mysite.com web server.

This allows the client to receive the same content, but instead of decrypting it with FairPlay Streaming it decrypts it with a clear text AES key in the media framework. If the content still does not play after performing the above changes, you probably have a content authoring issue.

With regard to the minimum version of iOS supported by FPS, it is iOS 6 and above.