Strange problems with corporate iOS application

I am responsible for developing my own enterprise application for the company I'm working on. I ended up in a huge roadblock that I cannot understand.

The application uses audio devices, I have 3 iPhone:

3gs - iOS 5.1.1 4 - iOS 5.1.1 5 - iOS 6 

using the provisioning profile, I can run a test build on these devices, and everything works fine, using my own developer account and a special profile, they all work fine. Build it for wireless distribution with the enterprise, and all iOS 5.1.1 devices do not work.

There is no problem with the installation, the applications load correctly, but the audio devices + circular buffer that I made go to hell. It looks like I'm getting a massive buffer overflow, but I canโ€™t understand why, only with the enterprise account, what is happening. I get all the correct data, the data is correctly delivered to the sound, and if I increase the circular size of the buffer very high, I can correctly reproduce the sound here for a very short time, and then it becomes foggy and comes back for a short time and the fog passes again.

I am wondering if anyone knows of the main differences between a test assembly and an enterprise assembly. Is it possible that there are some best practices that I donโ€™t follow, because I canโ€™t understand why I see such huge differences between them.

Note: The only changes to the settings that I make between 2 lines are code signing, nothing else

+6
source share
1 answer

Without posting the code, I can only guess. Most likely, the Enterprise build will compile with optimization, while your test builds will not. You may have introduced undefined behavior that causes your application to malfunction during optimization. I recommend starting the analyzer over the code and fixing any problems, as well as starting the profiler. An example of compiler optimization causing problems can be found here: Compiler optimization, which makes the program run slower

+1
source

All Articles