iOS 6 Streaming Player Com.Apple.Coremedia.Networkbuffering Bug

iOS 6 streaming player com.apple.coremedia.networkbuffering bug

I was having the exact same problem...

try to do this just after you instantiate your player:

[player prepareToPlay];

It should be called automatically when you call play but apparently on iOS 6 something goes wrong if you don't call it explicitly.

In my case it solved the problem.

Error getting audio input device sample rate: '!obj'

I was trying the above code on a virtual machine and turned out that the VM had problems with the audio configuration. Tried the project on a macbook and it works fine.

MPMoviePlayerController Simulator Crash

Solution: Remove the "All Exceptions" from the breakpoint tab.

This answer is from Till's comment above. I had this problem and I almost missed the answer because it is a comment. Till's answer helped me, so I hope this helps someone else like me.

exception

What does this gdb output mean?

That is a confirmed bug of the iOS SDK 5 / Simulator - happens as soon as the simulator tries to play sound (from a movie or any other sound source). Do not worry though, it won't be a problem on the actual device.

You mentioned actual reports of users having trouble using your App - those problems are not related / connected to the issue you have posted above.

This issue is filed by Apple under Bug ID# 10555404. I did file a report myself which has finally been identified as a dupe of the mentioned bug id.

The issue currently persists up until and including Xcode Version 4.4.1 (4F1003), iOS SDK 5.1.

Update

This issue is finally fixed within Xcode Version 4.5 (4G182), iOS SDK 6.0.

Note

The issue persists even in Xcode Version 4.5 when used in conjunction with the iOS 5.1 (or lower) simulator.

How to check network connection type in Blackberry?

Your question springs from an incorrect assumption. A Blackberry could be communicating over any or all of those channels simultaneously. In fact any application may as well. At any particular time you can determine if coverage is sufficient for one of those channels, or register a listener for notification of changing status using net.rim.device.api.system.CoverageInfo.

Managing CSS conflicts

The best thing you can do is assign areas of responsibility - if you are all working in the same area of the site you are bound to have conflicting changes and will only create difficulties for yourselves because you will constantly be stepping on each other's toes.

Once you have established a common baseline for the styles of your site, divide the main areas of the site amongst you and only work in those areas. When changes need to be made to the baseline, make them out in the open and communicate with your teammates about this change so that no one is surprised.

I am not going to pretend that this is easy to do - working on something as a team is a challenge that the entire software development industry has yet to completely solve. Good luck!



Related Topics



Leave a reply



Submit