So i have been having the hardest time getting my iphone application approved. And i sorta when on a little rampage through some of my code.
In my shear stupidity I thought that maybe I did not need the SenTestingKit.framework. So i attempted to remove it from my program, and when asked if i would like to delete or remove references i accidently clicked delete.
However upon reviewing some crash logs PRE-Deletion of SenTestingKit.framework I found the following...
Again this error was before I deleted the framework. The crash code to this is 0xe7ffdefe
Could someone please tell me where i might get the sentestingkit.framework from? And also if you have anyidea why it is causing the crash that would be so amazing to hear.
Thanks!!!
To restore that framework, just re-install Xcode. Or maybe your trash still has it.
About the iOS devices that complain about not finding the SenTestkingKit: I'd assume so, as it's a Xcode-only framework used for test cases. You aren't supposed to link it when distributing the app. Why would the user want to run test cases?
Related
I'm not completly sure if it's proper to ask this here, but...
I'm a student forced to work with Code:Blocks IDE on Win7 (64 bits), and it keeps crashing everytime I try and add/edit an #include, I've tried in both C and C++ and I think it's got to do with the editor since it compiles correctly.
Has anybody else had this problem? Is there any way to fix it?
Best bet would be to search through the Code::Blocks ticketing system to see if anyone knows about the problem.
If no-one does, then raise a ticket yourself.
It'd also be a good idea to provide as much information there up front as possible, such as the source files (or enough of them to cause the actual problem), project settings, IDE version, and so on.
That'll get your ticket moving along faster than if they have to chase you for the information.
I am trying to use the Registration by Convention feature of Unity in a pretty standard MVC4 app. I'm using the following code...
unityContainer.RegisterTypes(AllClasses.FromAssembliesInBasePath(),
WithMappings.FromMatchingInterface,
WithName.Default,
WithLifetime.ContainerControlled);
Here's my problem. If a rebuild is done on the solution, the registration works perfect. If I go right back into debugging the app after I end it, not causing a build, the registration does not work. It appears to add some registrations to the container, but not all.
Has anyone ran into a similar problem or have a solution to this one? I'll provide any additional information that is needed, but I'm assuming this one will only be fixed by "I've seen this before" :)
I have an iOS application that is exhibiting performance issues. The problem is that the developers can't reproduce it. And the user who can reproduce the problem is physically nowhere near the developers. This means we can't use Instruments to help debug the problem.
Is there anyway we can do method level timing?
You can say to the person who makes the proves and have the issues that send you the debug log of the crash. The developers could try to find the problem with it.
I have a project in which I'm taking reference of another library. I have changed something in the classes of reference project. How do i find that crash is occurring because of the changes. Gdb shows nothing when application crashes.
The simpliest way i see is testing without the changes you made, and see if the app is still crashing...
If you find out the modifications are not the source of crash, post some code, it will be better to solve your problem.
It seems whenever I go to use the debugger in my project xcode decides to get caught and shows the pinwheel indefinitely. (haven't waited more than 5 minutes.) The strange thing is that this is only happening with one of my projects, the other ones are working fine. I can mouse over a variable and it will give me the information and everything, but in my one application, not such luck.
Is there a programming error that would cause such an issue? Or is there a possible solution to this problem? Thanks in advance for any help!
It sounds like there might be an infinite loop somewhere... Otherwise I have no clue. Try rebooting your Mac. Try simulator versus device.
I honestly have no clue what the problem was, it stopped doing it all of a sudden, then I did an update to xcode and it has not done it since. It probably just caught a hitch somewhere. whatever. Thanks for your help!