I've been having this issue for quite sometime now. Basically, when I cannot copy something from my web browser or a file and paste it into the simulator (ie in an UITextField for example). I read multiple questions here, I tried the suggested answers, but nothing works really.
When I copy something from my web browser for example, I have Automatically Sync Pasteboard activated in my simulator and yet, cmd + V doesn't paste it. Even though I've copied the data, I have no edit > paste menu activated in my simulator. Even if I disable Automatically Sync Pasteboard, I dont get the edit > paste menu. I'm testing this on iPhone 8 simulator.
Is there a way to fix this?
I was having the same problem.
I turned the Automatic Pasteboard Sync off and on again and it started working.
I searched for an answer for this for some time. For Apple Silicon (M1) I eventually found a page where some users had tracked it down to an issue with iOS 14+. When I installed switched to a simulator iOS 13.7 as instructed (see link) pasting worked again. While this is clearly not what was going on with the original question (10 years ago!), I am pasting here in case someone else has this issue.
Copied from my answer here.
Related
I am new to iOS development. I was opening the .xib file in the editor and tried to make an iPad version of the app. I went to File > Make iPad Version. An iPad UI appeared. I closed it and didn't save it.
The problem now is that the app is now crashing when viewed from an iPad.
Thanks!
Here's an official answer or, to be more precise, a couple of useful tips from someone who is also new to ios development (4 months):
First of all, update your xcode version. If you are new, there is absolutely no point in starting with an older version. True, it may have a bit more tutorials but it's not that hard to find stuff for xcode 4. Trust me, been there, done that ;)
Second, if you run your app on a device and it crashes, you will get a crash log. Connect the ipad to your pc and open the organizer window from xcode. There, go to Devices and select the logs for your device. The log will help you detect the cause of your problem.
Third, when you will encounter more problems like this in the future, be more detailed when asking for help on stackoverflaw. Post more info, error logs, print screens, etc. Basically, anything that could help others help you
I've imported an iPhone app that I have developed for iOS and am now maintaining it. I've came across a couple of bugs when trying to add to the iPhone's calendar, which I'm happy to try and sort out myself with a bit of debugging.
One problem is that when I go to run the application on the iPhone simulator, it seems to run an older version of the app than the one I am running. I've removed and added another button since then and the old button is still showing when I run it in the simulator. However, when I compile and run this on a device, it loads the correct version and displays the correct version number in the 'about' view.
But... my main problem is that it doesn't seem to debug on the device properly. The app actually works fine except for the calendar problems, but if I put a few breakpoints in so I can see exactly where this is going wrong, it just doesn't seem to step through! The app pauses, and Xcode says the app has paused! I can press step over and continue execution etc and it appears to work, but I can't see it stepping over the code, nor can I hover over variables to see their values.
I've tried reinstalling Xcode multiple times (I did have a problem installing an older version, so I had to wait until the next version was available before Xcode would install).
The stress is: Today is my last day at work, and I'd really like to get this app ready for iOS 5 before I leave.
Has anyone seen these symptoms before? Is there a debug setting that I've missed? Or is it a corrupted installation?
I wish I could help people a bit with more information, but I don't even know where to start looking here. Any code I can post? any settings? (not too familiar with this, I'm a .NET guy usually).
Thanks!
Sorry you're going through a tough moment there Connell; as you said you're not too familiar with all this, I'm laying down a few steps which might help you out. Some are pretty basic, yes, but I've resolved to these steps myself several times when I've encountered similar scenarios;
If you're testing on the simulator, do a 'Reset Content and Settings' from the 'iOS Simulator' main menu. This will remove all old data and settings and give you a clean start.
Do a 'Clean All Targets' from the Build menu. Then go to your physical project folder and delete the Build folder from it altogether before starting to build again.
Restart both XCode and the Simulator (and your Mac too if possible)
Make sure the mode is set to Debug and not Release or Distribution
Even on the device, remove the old app before putting the new one in, and restart it for good measure.
Delete all Provisioning Profiles from the device and install just the one you need.
On the code;
I've noted that the app appears to 'pause' like this a couple of times when I had accidentally created an infinite loop in the code. Double check to see whether there's something which may cause this.
Unless you haven't already done so, throw an NSLog or two in there to see if its really not being executed beyond the breakpoint.
I've had the exact same problem with a project that I started on xcode 3 and then switched to xcode 4. What fixed it for me was changing the compiler in the project settings.
The default compiler up to xcode 3 was gcc, while the default compiler on xcode 4 is LLVM gcc.
Now, I don't know exactly what's the issue that gdb could have with LLVM gcc, but switching the compiler back to gcc in my project settings and doing a clean build fixed my debugging issues.
Might be worth a try.
Have you checked which debugger is being used GDB or LLDB? Select Edit Scheme from the Product menu, and see what the Debugger setting is under the Debug scheme. You could try switching between GDB, LLDB, and None and running in between.
Today, after installing Xcode 4 with the 4.3 SDK, I attempted to launch my application. However, the application will build and the iOS Simulator will pop up, but I get a message in the window in Xcode that says "Attaching to YourApp" which stays there indefinitely. How can this problem be fixed?
I had the same problem, that is, when I launched my application in the simulator, Xcode was hung waiting for the simulator to start. The simulator showed a black screen - nothing at all.
Note this is a project that ran fine on Xcode 3 and is the exact set of files used to build the application that is currently for sale at the App Store.
Okay, so here's the underlying problem, and my solution:
My application name was "ultimateTimer.app", as seen in Xcode under the Products folder. However, this was NOT the name in the project file.
Here's how to found out:
Click on your project in Xcode (it's usually at the top, e.g. mine is called ultimateTimer.xcodeproj). Under "Build Settings" tab, look for the "Packaging" area and specifically for the "Product Name" variable. Under Product Name, I had three entries:
Debug
Distribution
Release
Under Debug, it had the value "TalkUltimateTimer" which was an old name of mine. When I changed this to "ultimateTimer" to match the "ultimateTimer.app" as above, I found the Xcode attached to the simulator correctly.
This happened for me for iPhone applications. I opened the simulator myself and switched the device to iPhone Retina Display and from then on it worked. I tried switching back, but it didn't work again, so I have had to keep it on the Retina Display simulator, and if I need to test non-Retina Display I'll use the iPad simulator.
I skimmed the post and these seem to be the two solutions thus far:
I think I figured out the problem:
I went to 'Edit Schemes', and for some reason, the scheme I was using was pointing at BumpDev.app as the executable instead of bumpdev.app. Changing this made things work. Perhaps there is an issue when converting from xc3 proj files?
Anyways, the app now boots in the simulator. Yay!
And the other solution in that post is:
Did your project by any chance have a folder reference with images in it?
For me the problem only happens when I have a folder reference in the project. When I remove the folder reference and instead add the folder as a group, clean the project, and hit launch things work fine. In the "Copy to Bundle" phase each image is then listed individually, whereas when I had a folder reference, the whole folder was listed.
This took me a really long time to figure out. It was quite frustrating, but I'm glad I have a workaround until the bug is fixed.
I had the same problem after swapping the mouse for a new one. restarting my iMac resolved the issue.
I just upgraded to Xcode 4.3.2 and had the same issue with new projects. After poking around and comparing projects, I found out that new projects were set to the LLDB dbugger and the projects that worked were using GDB.
After changing the debugger for the new project to GDB, it worked. I am yet to research what the differences are, but at least I can now run my new projects.
Ensure you are starting a proper scheme.
I. e. when using CocoaPods, running Pods scheme would not start emulator.
It's a known issue. Have a look at this thread in the official forum.
Hey, update Xcode to 4.0.2. Problem solved :)
I had the same problem, I tried every solution here, but no works. Finally, after I rebooted my computer, the problem was gone.
Restarting the simulator worked for me
I've been developing iPhone applications for a while with Xcode. But since this morning, my debugger console doesn't display anything anymore. I've reinstalled Xcode, but it doesn't help.
Has someone had a similar problem? What can I do to repair it?
Thanks for your help.
If the console doesn't even display the welcome message maybe see (in Xcode preferences) if the font you are using somehow became corrupted. Also see what foreground color you have assigned for the font and that it isn't a white color. If you click in the console window is there text that is not visible but that you can select?
If so, try Cmd+C and paste it in TextEdit maybe. Also try switching the debug prompts to another font. You will find the settings for switchings those prompts under Xcode prefs > Debugging in Xcode 3 and under Fonts & Colors, I believe for Xcode 4. Even though you did re-install I can't remember if the preferences plist will get deleted in the re-install. The Xcode preferences plist should be under ~/Library/Preferences/com.apple.Xcode.plist. Try renaming that file temporarily before starting up Xcode.
If the console does display the welcome message but you get no output from your program see if you are using an NSTask and setting stderr to be used for your own output. I had this happen once but I was also using SenTestingKit at the time to do my unit tests and somehow it ended up to where noone was able to print to the console - not my cli program and not the testing kit.
As a last resort, Xcode 3.2.4 is out since a few days.
I had the same problem, after I created a new scheme for testing target according to Apple Unit Test Tutorials. I was seeing only (lldb) message at the top left corner and nothing else. I deleted this scheme and it started working normally. I think, I made something wrong, when followed instructions.
So, try to delete schemas, except the main one.
To anyone wondering why console output isn't shown in tests, ensure the following is selected in Xcode prefs:
Today has been a headache - first my upgrade to xcode 3.1.3 trashed all my certs/provisions. After two attempts, I got them fixed.
Now, I'm dealing with the issue in the subject, no console output.
Absolutlely nothing is getting printed to the console - No startup info, not when I "print" a variable from xcode when stopped on a breakpoint,
not NSLog() either.
Nothing.
I've restarted my Mac, restarted Xcode, etc. I've made it so clears the console and opens it on project build. I had GDB log to a file,
and that works, so the plumbing is cool. Its just the console itself is dead.
Image: (and this is after attempting to print the contents of a variable while the app is running)
http://mr-sk.com/iphone/screen-capture-2.png
It doesn't seem to matter if I'm on the device or the simulator ...
That looks like the split bar is pinned all the way to the right side. Look for the dimple and drag it back toward the right.
I'd also try asking in the iPhone developers portal forum, since you can ask about beta versions of stuff there...
This is an older post, but I just recently ran into this with 3.2.3, so if someone happens upon this the answer by cdespinosa was spot on, however many of us "noobs" may not know exactly where to find those files, so just in case...
Go to Finder, find the folder where you have your .xcodeproject file and right click on it and click on show contents of this package. When the new window appears, move the .perspective, .mode, .pbxuser files to trash. (Make sure XCode is closed when you do this...I happened to do this while the project was open like an idiot and didn't think it worked the first time)
Now reopen xcode and your project. Your console should now be fixed.