I've just installed OS X Lion and XCode 4.1.
I have an app that opens the last used document automatically at startup. To do so I have implemented applicationShouldHandleReopen.
This app used to launch fine from XCode 4.0.2 on Snow Leopard.
After I compiled my app with XCode 4.1 it stopped working.
I put a break point inside applicationShouldHandleReopen, but it never breaks unless I click on the app icon on dock.
When I double click the app in Finder as opposed to running it from XCode 4.1, it works as expected; it launches the last document, meaning applicationShouldHandleReopen must have been called at startup.
Any ideas what happened? What should I do to bring back the old behavior?
Or do you think this is a bug in XCode 4.1?
Thanks
This is no longer an issue. I don't observe this behavior any more.
Related
I have been building mac app on my mac mini and it always worked well but today i faced this error, searched a lot but no luck.
Message from debugger: unable to attach
What i tried:
Clear derived data
Quit Xcode
Restart machine
installation directory set to blank and also to /Applications
Tried Skip Install No / Yes
Using developer Signing certs
M using only Developer certificates and not provisioning profile to sign my cocoa app
Xcode 8.2
OSX 10.12.1
Please help :)
This is what fixed it for me, perhaps it will help others but I do realize the question was for 8.2. I had it set to Xcode 9 "New Build System" disabling this and switching to "Standard Build System" in the Project Settings under the File Menu. I had tried all the other things like killing DerivedData, clean build, restarting Xcode. I also verified that my dependent libraries were set correctly. The only thing that worked was disabling new "New Build System"
I just had this problem today. I have little demo code in a mac project(created with Xcode 9.4). This error just started to occur after I upgraded system to macOS Mojave 10.14. However, in Xcode 10 this project runs no problem(without changing anything). If you can use Xcode 10 it will probably be fixed.
Unfortunately, the above solutions didn't work for me (although I am sure they work for some people).
Here is what worked for me, in case this helps anyone else:
Close Xcode
Open Xcode and Create a new Xcode project
In the iOS template, select Single View App then click Next
yes, I know you are trying to get a macOS app attaching to the debugger :).
Give the iOS app any product name and organization identifier you would like and click Next
Create the new project anywhere you would like (I saved it to my desktop)
Build and run (cmd + r) the iOS app on a simulator like the iPhone 8 (starting a simulator and running the iOS app will take a little time, so have patients)
After the iOS app runs in the simulator, click to stop it from running (the stop button is next to the run button)
Open your macOS app that you are having trouble connecting a debugger to, and build and run it (cmd + r)
This, for some reason, allowed me to connect to the debugger with my macOS app...
Xcode version: 10.1, macOS Mojave version: 10.14.2
I recently updated my Mac software to OS X El Capitan. Xcode started crashing repeatedly! Whenever I tried to create a new file, it crashed. So, I updated it to Xcode 7. Now, whenever I create a new file, the beach ball appears and the application stops responding. I end up force quitting. This happens with every project. Whenever I click on any file, the same happens. I really need an answer to this as soon as possible because I am partly dependent on Xcode.
I'm developing a background only OS X app in Xcode. I've archived the app and placed .app file in /Library/Input Methods/. It's running fine. Yesterday, every time I modified something & then run it in Xcode, newly built app would run instead of the one I placed in /Library/Input Methods/ and I could see the Console output of the newly built app.
But suddenly today this doesn't happen. The one in /Library/Input Methods/ runs and nothing is shown in console. Also when I run the app in Xcode, I can see two instances of the app in Activity Monitor (one from /Library/Input Methods/ and other one from Xcode).
I'm using Xcode 5.1 and OS X 10.9
I tried quiting-restarting Xcode, restarting Mac, cleaning project, deleting data in Derived Data folder etc. But nothing worked. Any help would be highly appreciated. Thanks in advance.
Figured it out. I had to run the app from Xcode BEFORE it gets started from the system i.e. by changing input method. So the app process of Xcode build needs to be run first.
Τhe last few days I experienced a problem with Xcode 4.6.2 when I try to run twice an application, in IOS Simulator only, the program throws an exception.
Somehow the simulator keeps the instance active even though the stop button was pressed and requires to press it again many times in order to run it again,on the other hand in my device Xcode works properly.
Any ideas ?
Xcode 4.6.3 was just released to fix a hang/crash issue with the ios simulator (and lldb debugger), particularly on osx 10.8.4.
I installed iOS 4.2 on my 2nd-generation iPod Touch last week. I tried running my application on the device through Xcode, but it didn't work (because Xcode didn't yet support iOS 4). To solve that, I installed Xcode 3.2.5 and the iOS SDK 4.2. Now I can get the app to run in the iPhone/iPad Simulator just fine.
However, I can no longer select "Device" from the menu at the top of the screen. It's a choice, but when I try to click on it, it never actually gets a check mark.
Because of this, I can no longer run the app on my iPod. The other (related) problem is that I can't choose "Build and Archive" from the Build menu anymore because the target is not a device.
Why is this happening? Do I need to change some settings in my project, or something with my device itself?
EDIT: Upon closer investigation, it appears that I can't select anything but the iPhone Simulator 4.0. Maybe there's something wrong with the project file.
Check that the base SDK is set to Latest iOS (currently set to iOS 4.2) for your Xcode project and your target's product, then perform a rebuild and see if your iPod is recognized.
Also try visiting the Xcode Organizer and see if it's asking for anything from your iPod. Typically Xcode will want to collect some data from devices whose OS receive updates, so it can update itself and install your apps on the updated OS properly.