Happily working in (as much as you can ever be happy in) Xcode 4.5.2 when modifying a storyboard, Xcode crashed.
Ok, no worries, Xcode crashes all the time. Restart it we are stuck. I get the little spinner in the middle of Xcode as it attempts to open the three tabs I had open. But eventually stops responding.
After I force quit, I notice a single process that is still left running:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Overlays/Interface Builder Cocoa Touch Tool --socketFD 30
I can sudo kill -9 this process all I want, but every time I open this project in Xcode, repeat performance.
Using the alt+shift+click trick for Xcode in the dock, I can open up a blank instance an open a different project just fine. No issues loading the storyboard view or anything.
I traced the issue to the one iPad storyboard I was working on. After doing Google research I opened up the storyboard in another editor and changed changed useAutolayout="YES" to useAutolayout="NO" and I was able to open the storyboard just fine in Xcode ... but none of my objects were there.
I could keep on pontificating... but I'm really hoping one of you have seen this before. Thanks!
This isn't an answer, but I had a similar experience. One thing I noticed was if I edited the Storyboard manually to disable AutoLayout, the UI objects were all still in the Storyboard, just with a height / width of 0. Not terribly helpful, as you still pretty much have to recreate everything from scratch (or at least since the last saved working version).
Xcode was crashing at load for me due to one pesky little misplaced tablecell. I couldn't load the program at all or import the storyboard and every solution I saw online failed. What I did was delete the story board, open the project, and then restored the most recent snapshot (always take snapshots!). It imported the previous storyboard and I hardly lost any work.
Related
My app is using Firebase Analytics and I believe starting in iOS 13.2 started getting the errors described here: Why I get the console warning: [Process] kill() returned unexpected error 1 when I load a WKWebView in iOS13.2?
I guess it wasn't a big deal
Since I planned for my app to go live in January, I began bigger tests in physical devices. I noticed after a while the app started to behave erratically, specially after receiving a [general] Connection to daemon was invalidated error. This doesn't occur in the simulator
Searching the internet I found a post that describes the same problem: https://forums.developer.apple.com/thread/124306
In my case, only Firebase seems to be calling WKWebView, but every time I open the UIMenuController I get the error described in the console and the app appears to be missing inputs. This is specially troublesome with UIScrollViews, which my app uses a lot. The pinch gesture seems to work at will. On an iPhone 6s, the issue isn't as noticeable, on an iPad, it's like a 50% chance the pinch gesture will work properly
Outside of removing Firebase, is there a way to mitigate this issue?
1 June 2020: The console message still persists, however, I have seemed to resolve the UIScrollView issue by deactivating delaysContentTouches, now the pinch gesture seems to work most of the time
23 October 2020 If anyone notices their app starting to behave erratically with no apparent reason I HIGHLY suggest to test it on an iOS 13 physical device if possible. Seems that Apple removed the warning from iOS 14, but testing it on iOS 13 you can pin point the exact reason after the warning appears in the console
Upon further testing, I've reduced the view down to a dead-simple UI view with a single SwiftUI TextField and the 'Connection to daemon was invalidated' still appears after I type the first character into the field. Soon thereafter the app crashes with a sigAbort. (So I don't think the reason is the UITextView wrapper I was using in the previous post). Once the invalidated message appears the app is doomed to crash, not right away but soon thereafter.
I have no idea what causes the 'invalidate' message and a Google search seems to imply that no-one else does either. Some folks appear to have made (experimental?) changes to their UI that stops the message but it appears to be impossible to determine a definite cause. (and like before it only occurs on a real phone)
Same issue without using Firebase at all. What I did: Delete build folder and compile again. Issue does not appears again.
On Xcode:
Clean the Build Folder
This will delete all of the products and intermediate files in the build folder. To clean the build folder you can use the shortcut Command+Option+Shift+K or Menu Bar → Product → Hold Option Key → Clean build Folder.
On Flutter:
Just delete build folder.
I recently downloaded the Xcode 8 beta. When I try to open the simulator, it gets stuck on the black Apple screen and I get a crash message for "SpringBoard".
Any ideas? I'm happy to edit if I left out anything.
Thanks in advance!
This is a known issue that is mentioned in the release notes and is related to issues in the download and install process. If you don't follow the installation instructions exactly, you can trip over this issue.
The workaround is rather straight forward:
Using Finder, copy (DON'T MOVE) Xcode-beta.app from /Applications to ~/Desktop
Delete /Applications/Xcode-beta.app
Move Xcode-beta.app from Desktop back to /Applications
I had a similar problem which, with a bit of googling, I managed to solve as it happened with the Xcode 6 Betas too. First of all, make sure that your Xcode-Beta.app is in the Application folder of your computer. Then go Xcode -> Preferences -> Locations. In "Command Line Tools" you will probably find that you have Xcode 7 selected. This is a problem that occurs with having 2 Xcode versions installed. Change it to Xcode 8.
After this, the simulators were still broken for me, so I went to Xcode -> Window -> Devices and delete all of the simulators. Then try a full reboot of your computer. Reopen the devices page and add in the simulators that you would like, and then right click on the Xcode app in your dock, and go "Open Developer Tool -> Simulator". Check that it now boots correctly. If its working so far, then you should be good to run your application. Otherwise try yet another reboot, just to make sure Xcode is refreshed.
Hopefully this solves your problem like it did mine, let me know if not.
SpringBoard failed to launch application with error: 0
If you get above issue make your simulator active window and follow step showed below in picture..
Note : It will delete all app from simulator..
I am able to work in the Source view with no problems. However, as soon as I click Design the source freezes and hangs. The same thing happens when I switch to Split as well. I cannot find much documentation/support for this issue and wondered if anyone else ran into this as well or has a potential fix?
Firstly please make sure you have selected the project/solution you are working on ,on the left bar (esp. if working with multiple projects.)
When that is done, clean and rebuild your solution. When this is done , try again.
If all fails, restart your machine and IIS (in that order) and try again.
I am using VS2010 on Windows XP pro (sp3, x86), and I just installed the hotfix kb2106584. This fix was reported by some people, example here, as having a fix for an issue I had with Asp.Net Development Server not getting opened properly from VS, which I was having previously. My issue was being caused by ESET NOD32 messing with the http traffic from devenv.exe and causing all the ports in my computer to get used up, however.
Anyway, as soon as that was finished, I opened my website back up, and clicked debug. Asp.Net Dev server pops up, which was what the hotfix was supposed to make happen, and then notepad++ opens with the tabs I had last time I used it, and IE never shows up. "Wait, what?" try it again. and again. Always notepad++, never IE, always with no new documents opened, just some completely unrelated stuff.
I've seen one other post on SO about this happening, here, but his issue was corrupted files/filesystem. My project is in source control, so I tried a delete&revert to yesterday's revision. Still opens notepad++, so that's not my issue.
I've also tried rebuilding, which did nothing, and deleting my local Solution files, which also did nothing. I restarted the program and then the computer, both to no avail.
I start to believe that this is the hotfix screwing things up, so I try to do a system restore to a couple days ago. Once again, no dice; it's still pulling up notepad++ instead of IE.
So, the questions become:
Is there a setting or two I can try changing to make it open the proper program again?
Or was this a bad/improper hotfix, and if so, how do I uninstall it? It doesn't show up in the Add/Remove Programs dialog, and I don't see an option to uninstall it in VS, or in the installer.
Thanks in advance.
[edit] Also note: Notepad++ is not actually opening the website file, it's just getting opened with whatever I left in it last time. I dunno if this helps at all, but I felt like details would be appreciated. [/edit]
Fixed:
Uninstalling n++, deleting EVERY registry entry & folder containing 'notepad++' (except one, from whose string I removed ";notepad++.exe"), then reinstalling n++ made VS stop opening notepad++.
Now it opens the default web-browser again.
[edit]
Note for anyone else out there who ends up with this specific and bizarre problem:
It would be worth a shot to try changing the "Browse With..." setting in VS, by r-clicking on Default.aspx to "Internet Explorer". My list included Notepad++ as an available internet browser.
This might be a better solution than the previous, if it does in fact work.
I didn't know this setting would allow Notepad++ as an option until I had to set it back to IE again after all this, and that may have been the problem all along. Apparently, VS just changes this setting sometimes. How or why N++ got put in as an internet browser is completely beyond me, but I did myself the favor of 'Remove'ing NotePad++ from the list, and you may wish to do the same.
Again, I'll never truly know whether or not I nuked everything when I could have changed a single setting that got mysteriously reset, but may this [lesson?] at least be recorded for posterity.
[/edit]
It took all of that to figure out that it [was?] a bogus registry entry somewhere that [may have been?] modified by the hotfix; a registry entry that neither notepad++ nor visual studio 2010 ultimate would clean up on uninstall or replace on reinstall
Which was it? I have no idea. Like I said, I didn't even use n++ this week until VS started opening it for me, and the only change I made was to install that hotfix.
Allope,
I've recently bough Flex Builder 3 and I am completely dissatisfied with its reluctance to debug. It manages to debug a few times, but after that, it just doesn't want to "connect to the debugger".
Help?
There is no easy fix for this. You now have to join the rest of us waiting for Adobe to update Flex Builder with a fix they say they have.
You can find the long sad story here: http://bugs.adobe.com/jira/browse/FB-16153:
Basically, this is an issue that has been around for months. Adobe says it has a fix - however - they've not released that fix yet. Adobe reports it's a threading issue...
For the rest of us (waiting for this) - if you need to move forward you can:
A) Live with the problem (painful)
1) Note that in the bug text there are several attempts to work around this - sometimes people find ways to soften the issue - but no one reports a full fix
2) Note that people trying the LocalHost fix - sometimes report a gain in productivity - but in most cases they do not.
B) Switch SDKs from 3.2 (or 3.3) to 3.1 ---- No one knows why - but it fixes the problem (you can then include the SWFs you need for 3.2 directly
C) Develop on Mac [Not a smart ass answer - honestly - for whatever reason this bug is not on Flex Builder for the Mac]
Join the bug discussion - on Adobe's site - it's still active as people are still waiting for the fix.
Make sure you have the required Flash Debug Player.
http://www.adobe.com/support/flashplayer/downloads.html
If that doesn't help, you might have to re-install Flex Builder.
Are you running it on windows vista? It may be this issue:
http://blogs.msdn.com/expression/archive/2009/03/16/page-cannot-be-found-issue-when-previewing-via-expression-blend.aspx
The page is about silverlight, but I ran into the same issue a while back with the flex debugger, and had to add the following to my host file (which windows defender removed):
127.0.0.1 localhost
This is expanded more upon here:
http://circstar.com/FlashLabUnderground/?p=64
I've had similar problems but every-time it refuses to connect to the debugger i have justed downloaded and reinstalled the flash debugger and it works fine. It's a pain but until adobe do anything what can we do?
Have you the tried FlashDeveloper ide? you can build flex project with it and it quite frankly alot better than flex builder for code writing (not ui work).
Hope this helps
Jon
I'm not sure if you have the same symptoms, but I came across a similar problem on one of our development machines after installing Flex Builder 3. When trying to run our app in debug mode, flex builder took a long time to launch the app and eventually timed out, displaying some message about not being able to connect to the debugger.
I found this solution which worked a treat. While Flex Builder is trying to launch the app:
Go to the browser page containing your app/swf, right-click on the swf to bring up the flash context menu.
Select Debugger
Select Other Machine
Enter 127.0.0.1 in the text field
Click Connect and hopefully it works.
NB: If Flex Builder tried to launch the app in Firefox, the page never appeared. It was only when it launched in Safari that I was able to access the browser page and the flash context menu.