I just retested 631 on an iPad 2 against 9A334 with the one reproducible test case that was actually submitted to us. There is no problem here. Everybody else has reported the problem as fixed with this build so you are the only one so far with problems.
You are going to have to submit a simple reproducible test case for us. And you should probably file a new bug with Apple, noting that this is some how different than the other one.
But I’m going to lambast you guys a little again. You guys knew about this bug as early as iOS 5 Beta 4 and you did not report it to Apple (or us) until the end of Beta 7 when they had already code frozen. This was clearly an Apple bug and not a Corona bug because audio worked fine in pre-Beta 4 and all other platforms (Mac, Windows, Android).
The tragedy is that this bug would have been fixed by Apple in time before iOS 5 had shipped if somebody had reported it when it was first discovered.
You guys are paying Apple to get access betas. Understand that when you deal with Apple betas, you must report issues if you want them fixed. This is one of the benefits you get for paying Apple money. Once they ship, you are stuck with the bugs forever (because not everybody upgrades their OS version). Never assume somebody else has filed the bug (nobody usually has). And that is beside the point. The more people that report the same bug gives it a higher priority at Apple.
Example: If every Corona user filed a feature request for syntax highlighting for Lua in Xcode, we would probably have it by now. I think the actual number of people who have filed the bug can be counted on one hand.
This particular Apple OpenAL regression bug is insidious. I was very worried we would not be able to work-around it, but we got lucky. But if your reports are true, then be very worried.
[import]uid: 7563 topic_id: 15991 reply_id: 59381[/import]