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.
Related
While developing a Cocoa sandboxed application, I discovered that if I switched it to non sandboxed, in all the Open Panels of the application, the right click commands (Duplicate, move to trash etc.) do not work any more. I am certain they did work no more than two weeks ago, but I have reverted the project to old commits and the misbehaviour is still there. I tried everything, until I realised that this misbehaviour now appears in all my projects, if I switch them to non-sandboxed. This makes me think it may be some kind of bug introduced in 10.14.2 or something similar. I hope somebody else has experienced the same issue so that we can understand better what is going on. Thanks
P.S. I am using the latest Xcode 10.1 (10B61) and tried on several machines. It is the same misbehaviour.
The OS might be confused by having some contradicting leftover knowledge about sandboxed and non-sandboxed versions of the app with the same version / bundle ID / signature.
Some things to try:
Test the app on a fresh user account.
Delete the app sandbox container from your Home Folder > Library > Containers.
Temporarily change app bundle ID to something new to see if it’s still affected.
I am using IBM's MobileFirst Platform Foundation (6.3.0.00-20150130-1638) to build an Android and iOS application. The application (iOS at this moment) gives quite a lot of information when running. But one is quite common and I think it is also quite dangerous. The error I get is:
THREAD WARNING: ['WLApp'] took '11.354004' ms. Plugin should use a background thread.
This is for WLApp, but for more plugins like DeviceAuth (111.884766 ms), UserAuth (19.232910 ms), another DeviceAuth (47.208984 ms) and more.
Is there a way to run plugins on the background, and so, how can I achieve this?
Another question is if I can and how to hide the Debug notifications?
These warnings come from cordova plugins, and it is harmless, it just means that the code in the executing part of the cordova native plugin side, should be run in background.
We are intending on cleaning these warnings out.
look at: http://docs.phonegap.com/en/4.0.0/guide_platforms_ios_plugin.md.html#iOS%20Plugins
You cannot do this on your own with the supplied plug-ins.
These warnings are issued by iOS but are harmless.
We'll take a look, but this is harmless, unless you actually see a real problem (which I doubt right now that you do).
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
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.
Can anyone help for the following ERROR:
Couldn't register com.india.XXX with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.
here m using xcode 4.1 and i have same project folders in my local desk.
When ever i open multiple projects with the same name its showing the above error.
Thanks in advance.
Some of the fixes that the links Saif contain may work for some, but not for me.
I have a very simple solution without restarting that will usually get you through the day.
When you get this error, before you do anything else, build for the other device (if you are running a universal application).
When you build for the other device, it kind of "overwrites" the process that creates this error. Once the other device is up and running, immediately build for the device that created the error. This will work most if not all the time, and will save you time digging through the multitude of fixes you will find in the other links.
I tried almost all of the fixes found there and none of them worked in my case. This works, but you should check your appDelegate for any bugs in your willEnter/didEnter (and other related methods).