Strange issues with iOS enterprise app - objective-c

I'm in charge of developing an in-house enterprise app for the company I'm working for. I've hit a huge roadblock that I can't figure out.
The app use's audio units, I have 3 iPhones:
3gs - iOS 5.1.1
4 - iOS 5.1.1
5 - iOS 6
using a provisioning profile I can run a test build on these devices and everything works fine, using my own developer account and an ad hoc profile, they all work fine. Build it for wireless distribution with enterprise and all the iOS 5.1.1 devices don't work.
There is no install issue, the apps load correctly but the audio units + a circular buffer I made go to hell. It seems like I'm getting massive buffer overrun, but I can't figure why, its only with the enterprise account that this happens. I'm getting all the correct data, the data is feeding into the audio correctly and if I increase the circular buffer size very high I can here the correct audio for a very short time and then it goes hazy and will come back briefly and go hazy again.
I'm wondering if anybody knows any of the underlying differences between a testing build and an enterprise build. Is it possible there are some best practices that I'm not following, as I can't understand why I'm seeing such huge differences between the two.
Note:
Only settings change I'm making between the 2 builds is code signing, nothing else

Without you posting code I can only speculate. The Enterprise build most likely compiles with optimizations while your test builds will not. You may have introduced some undefined behavior that causes your application behave irregularly when optimized. I recommend running the analyzer over your code and fixing any issues, as well as running the profiler. An example of compiler optimizations causing issues can be found here: Compiler optimization causing program to run slower

Related

Performance/memory analyzing tool for production OSX application on customer site

I need to be able analyzing Performance/memory issues which occurs on customer site for a OSX production application written with Objective-C.
As for now I found:
OSXPmem – it’s main drawback is that I need to dump all memory space to in to a single file(it’s not possible for me to transfer ~4GB or more from customer site - I can zip it but the bigger problem is that it not support 10.10 Yosemite.
Valgrind – Does not support 10.10 Yosemite.
Is there a good tool out there ? (such as WinDBG for windows)
BTW at development I use Instruments but in this case it does not help.
thanks for the help
Apparently valgrind will build, install, and work on osx 10.10 from the head of the development branch in the source repository, e.g. as per yosemite-and-valgrind and http://kalapun.com/posts/checking-c-code-with-valgrind-on-yosemite/
However depending on how the application works you may have more luck with the leaks command-line tool or the full-fledged Instruments tool, from Xcode. I haven't upgraded to 10.10 yet to try it there, but it should obviously still work in the latest Xcode for 10.10. leaks attaches to the running process, so is better for long-running processes that you can't shut down (cleanly), or for capturing usage metrics during specific operations.

Reset VS 2012 Windows Simulator settings

I was playing with the simulator that comes with VS 2012 and decided to crank up the resolution to see if my app would look well in high resolutions. Little did I realize how much that would demand from my machine. The simulator crashed and I haven't been able to use it since. I can start it outside of visual studio but as soon as I click anything it freezes and starts to lock up my machine. I'm running Windows 8 in a virtual machine so it's already a bit resource limited.
Is there a way (either through the registry or some other means) to reset the simulator settings? I need to turn the resolution back down so I can actually use it to test my apps.
This is definitely less than optimal, but I found a solution if you are desperate. I decided to repair VS 2012 to solve some other things and it seems to have reset the simulator settings.
This just further confirms that there has to be a simple way to do this because the installer probably just copied default registry settings in place with fresh copies of the files. Therefore I'm not going to accept this answer for at time so that others can see this and hopefully offer a better answer.

iOS Settings Bundle strangely disappeared

I'm working on some iOS app that involves connecting to a server and has an in-build Settings.Bundle which stored the hostname to that server.
This app has been prepared by someone else and is over a year old by now. The settings bundle and connection always worked perfectly fine, regardless of how they work. It worked this afternoon still when tested. Yet after lunch I came back and nothing worked anymore and I'm clueless on what the problem might be.
Before lunch I had some issues with an app with the same bundle identifier so I had this app's Bundle Identifier changed in the info.plist that I have been using to keep those matters in check.
Also I had been trying to create an .ipa-file for testing purposes. So I was busy with archiving the app. The app has an extern lib (zxing) to scan QR-codes for easy login functions. And my problems there were how to get the archiving file from the generic xcode archive to a genuine ios app archive. I succeeded by following this guide (http://pulkitsinghal.blogspot.nl/2012/03/wrong-archive-ios-app-archive-vs.html).
Which involved changing the 'Skip Install' setting to YES in the Target>Build Settings of my Zxing lib.
All done and well. Except, now I ran my app on my simulator and I couldn't connect to the server anymore. The hostname appeared to be (null), which was described in my Settings.Bundle.
I haven't touched the programming which created that settings item. So how could it have been disappearing on me?
Could it be that by changing the bundle identifier of the build settings in my mainproject and the zxing lib? Could it be something else?
Any thoughts on how my previous changes might have impacted the disappearance of the Settings.bundle?
(I could provide code of any kind ofc. but atm I wouldn't know what to post)
A possible solution could be reverting things back to an earlier revision of course, but I don't know what made it disappear in the first place. Or what could make it disappear. And wouldn't want to lose a few day's worth of work.

Strange application behavior when building a project with the latest xcode/OSX version

I have an OSX application written in Objective-C/Cocoa using xcode. The application is quite finished, tested and sold on the App Store.
I haven't worked on this application for some time and recently, I rebuilt it using xcode 4.3.3 on my OSX 10.7.4 and I noticed that while it builds just fine, there are some very strange visual glitches when running the application that were never seen before and occasionally, I get EXC_BAD_ACCESS when closing the application. All these seem to be related to the PDFKit framework I am using. I am unable to debug these problems since the glitches are just visual (nothing I can check in code) and EXC_BAD_ACCESS exception comes from internally allocated objects not related to my code.
The code itself haven't changed, I tried previous revisions of the code and they all exhibit the same strange behavior now. I tried running an old binary I have of the application (compiled couple of months ago) and it works just fine. Then I tried building it with previous versions of xcode, down to 4.2.1 (which I know was ok when I submitted the app to the app store) and the problems still occur.
Then I suspected this may be something specific to my environment so I built the project on different machine also with xcode 4.3.2 and OSX 10.7.4. Same results, the problems are still there.
So now I suspect that it has something to do with the OSX 10.7.4 update since this is the last thing that was changed between now and when I was able to produce a good build of the application. I am pretty puzzled to what to do next and how to identify the cause of this problem. I have an old binary that is working fine and I have a newly compiled binary of the same code revision that has problems.
Is there any useful information I can get from the difference of these binaries? What can I do to determine the cause of these problems? What can I try next?
Thanks!
NOTE (update): I stated it above but I want to make sure it is clear. This is a Mac OSX Cocoa application, not iOS.
just reset your simulator then try.
I hope you check the ARC information
go to your project Target set build settings --> Search Paths-->Always Search User Paths Set Yes.
And check your all class variables different from one another.
Xcode--> preferences-->Documentation check installed core Libraries (or) install it
like that
Xcode--> preferences-->Components check required component installed or not
check these things in your project.
Are you sure your customers are not having the same problem? Since you have tested the application on a different machine you probably do not have corrupt libraries installed (unless you did not install from scratch but used some migration tool?), so that is probably not the problem.
Most logical explanation to me would be that your customers also have this problem but they haven't reported it yet. In that case, you probably have a memory problem and there are techniques to attack that.
In any case, eliminate all the parameters that you can eliminate to simplify the problem. Deconstruct the application until the problem does not occur anymore or reconstruct the application in a different project until the problem occurs again.
It sounds like a nasty one, but you'll get there in the end, with patience and perseverance :)
First of all, you need check and verify the build log for suspicious compiler warnings.
For EXC_BAD_ACCESS, XCode analysis will give useful information.
You could try 10.6 or 10.5 (need manual installation) SDK. Or restrict the deployment target to 10.5 or 10.6.
I will answer my own question (since none of the above answers really answer it) so anyone with a similar problem might have a hint. I was not able to understand why exactly this happens but I'm pretty sure this is not a problem with my code but rather some glitch on Apple's side. And there is a workaround.
First, I compiled Apple's sample "PDF Annotation Editor" project on my Lion 10.7.4 and while the functionality is obviously different from my project, it also exhibited similar glitches with the PDFView display that my project does when compiled with 10.7.4
Then I proceeded to building a fresh clean system on new hard disk. Intalled Snow Leopard and upgraded to 10.6.8 and ONLY installed xcode. Compiled my project (the source code always stays exactly the same) and everything works fine. No problems seen in the compiled project.
Updated my OSX to Lion 10.7.4 and xcode 4.3.3, same source code. The problem is there after I compile it. I am pretty sure that if I tried 10.7.3 first, I would not see the problem as I remember it only starts with 10.7.4 but Apple doesn't provide any reasonable way to update to 10.7.3 first or downgrade to it after 10.7.4 is installed (shame on them, not very developer friendly!).
So, the problem appears in 10.7.4.
Then I installed the pre-release version of 10.7.5. This was the only thing that was changed, same source, same xcode. To my surprise, the compiled code works flawlessly now and the problems seen with 10.7.4 are now gone!
So my workaround - wait for 10.7.5 release before working on the project further. Hopefully Apple won't screw it in the future with Mountain Lion. I don't think I am going to try and debug it further or submit a ticket to Apple, going to be a tough case to explain.
Thanks for the responses.

How to use NSZombie?

So I just finished my app and I wanted to as the final few steps run some diagnostics on it. In terms of what its memory usage, allocations, leaks, etc are.
I have a few questions:
1) Is there a standard list of instruments/checks I should run on my app be fore its submitted to make sure its robust? If so could someone point me to some links and/or tell me some names so I can google the stuff.
2) One of the tools I know to run is NSZombieEnabled. I followed the steps I found online on some sites to set up this NSZombie test but it doesn't seem to be working. I looked at this site: NSZombieEnabled
This is what my XCode looks like after I tried the steps listed there:
But why is the zombies choice not highlighted?
Once I get it to work how do I actually use NSZombies?
So far from what I know, NSZombies is only available for debugging Mac apps or ios apps running on the simulator. It cannot be used for apps running on i devices.
Follow this thread and this.