3 ms·

I've worked in a music app that did something similar to what you are doing (encrypting the content). It was approved without any issue (along with various upda

by BSousa 12y ago

I've worked in a music app that did something similar to what you are doing (encrypting the content). It was approved without any issue (along with various updates). Are you sure the new encoding profile is really low bitrate (as in, playable in less than 3G connection speeds?) I'm not sure what is our lowest bitrate, but according to HTTP Live Streaming page ( https://developer.apple.com/library/ios/documentation/networkinginternet/conceptual/streamingmediaguide/UsingHTTPLiveStreaming/UsingHTTPLiveStreaming.html https://developer.apple.com/library/ios/documentation/networ... ) it should be 64kbps or lower: 'In addition, you should provide cellular-capable clients an alternate stream at 64 Kbps or less for slower data connections. If you cannot provide video of acceptable quality at 64 Kbps or lower, you should provide an audio-only stream, or audio with a still image.'

bfarrellforever 12y ago
At first, yes, we were definitely in the wrong. according to this directive we weren't aware of. We didn't have the low bitrate stream. But after we got rejected the first time, we fixed that and continued to be rejected. Once we got a hold of someone real at Apple they admitted the mistake and that's when we found out that they were trying to test our streams and giving us the form-letter rejection.