Every time I open the IDE it starts loading then shuts down before I get a chance to change anything. Remember this happening before on previous Versions of Xcode but I haven't had to deal with this in a rally long time. Any ideas?
PS. I think its Xcode 8.2.1 ,really hard to check when it closes down immediately.
Found that deleting Derived Data enabled X-code to start responding again.
Was difficult to find it though as most people were explaining how to find it from within Xcode :P If future me or any other super-devs would like to know the default directory then you can find it under the hidden folder Library on your user directory IE. /Library/Developer/Xcode/DerivedData/
Related
I'm on Xcode 13 GM (13A233) and I'm noticing that it won't stay paused when it hits a breakpoint. It stops, but about a minute later it just resumes. Is there a new default setting that might cause this? I don't see anything relevant in "Behaviors," but maybe I'm missing something. Has anybody else encountered this issue?
The only unusual thing about my project is that I am calling Python from it, using PythonKit. But this breakpoint pause issue isn't isolated to code involving PythonKit.
I've tried all the usual "fixes"—i.e., clean build, delete derived data, reboot, etc. The app is just a simple SwiftUI app for macOS.
This is actually the debugger crashing and the app detaching: The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log....
It doesn't do it my main View, but does do it in a static method called on a singleton in the app, and also at various points in a custom package I'm developing alongside the app.
I see a similar unresolved issue from August at bugs.swift.org: https://bugs.swift.org/browse/SR-15110?jql=text%20~%20%22lldb%20crash%22, In case anyone else is seeing the same issue (maybe you can post your log there).
UPDATE: I completely forgot that I was running on a dev snapshot toolchain. All good in Xcode 13.1 with bundled toolchain. Moral of the story; if something really strange is going on, check your toolchain.
Since I loaded build 1868 of VisualStudio for Mac, it has been randomly replacing the contents of an open tab with the contents of another open tab. If I don't notice and compile, it will then save those contents to both files which basically destroys one of my source files.
I loaded v. 7.7.1 (build 15) hoping they snuck a fix for the problem in there. If anything, now it's worse. I'm having to close and re-open VS every 15 minutes, or so, and digging up a backup to repair a corrupted file every couple of hours (when I don't notice and it overwrites a file).
This is REALLY slowing me down. I haven't been able to find anyone else complaining about this, which makes me wonder if it's just me?
I'm running on macOS Sierra (v. 10.12.6). I'm using Xamarin to develop a mobile application, and am currently focusing on the Android side (and will get back to iOS eventually).
Does anyone have any ideas why this may be happening? Do you have any advice besides remove then reload everything? Sure it's an easy answer, but takes a very long time to do with less than awesome internet speed.
Thanks in advance for your help!
-Karen
Not a programming problem per se, but rather a programming environment problem that I have been unable to find a solution to.
The problem relates to Adobe's Extendscript Toolkit (both 3.5 and 4), but so far I haven't been able to solve the problem, so here I am...
The error I get has appeared more or less over night. I didn't experience this problem yesterday, nor this morning. But exactly WHAT has happened is beyond me. I have removed preferences, I have uninstalled, reinstalled, created a new user, restored old preferences from Time Machine and I'm now pretty much lost for options.
Basically, nothing works in ESTK anymore. Just opening ESTK and entering alert('Hello') won't work. Neither will $.writeln(). Everything running from within ESTK seems to give the same error;
Cannot execute script in target engine 'main'
With details:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
Below is a screenshot taken from the new user I created to test, same problem.
The "funny" thing is that all the scripts (InDesign CS5, still hanging on to it for reasons) still work perfectly in the applications' script panels. So there is nothing wrong with the scripts (heck, they haven't changed one bit, and still refuses to run in ESTK).
As mentioned, I've tried installing the ESTK CC (version 4) as well, but the very same problem occurs there. Which leads me to think the problem lies somewhere else, but I do not know where, and why.
So, if anyone can shed any light on this issue, at all, I would be very happy. Debugging is basically the only thing ESTK is good for in my book, but now that even that functionality is gone, I don't know how to efficiently debug the scripts which is kind of hampering the workflow.
For reference, I'm running InDesign CS5 (from the old Creative Suite) on a 2008 Mac Pro with 10.11.6 (El Capitan) installed. Well aware that it's pretty out of date, but that is beside the point here.
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
Search for the value: 604800000 (line reads bt.timeout = 604800000)
Replace that value with 604800 and save
Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
I've been using MacVim (7.3 Build 53) on OSX Snow Leopard and every so often, the window will simply disappear, losing any unsaved changes I may have. It is always the active window (if I have multiple windows open, they are unaffected) and it doesn't completely quit MacVim since it remains open on the Taskbar, just with no open windows. There are no warnings or errors of any kind.
Normally to debug a mysterious vim related issue I would start by taking everything out of my config files and build them back up bit by bit checking if the error is still there however this problem is quite intermittent and (so far) I can't force it to reproduce the problem, so I'm not going to be able to tell for sure if the problem is fixed.
I've had a look for error logs and the such like but haven't been able to find anything. Does anyone have any suggestions for debugging this kind of issue?
One of my projects seems to be nearly impossible to search through in Xcode 4.3.2 on Lion lately. Using the search navigator to find anything in my project basically locks up my whole computer, with the beach ball, for 30 seconds or more.
I've tried deleting the project.xcworkspace file (which is very small anyway), and that didn't fix it. I've tried clicking on the Xcode activity viewer, but everything is locked up, so I can't see anything helpful.
With the Activity Monitor application, I can see the CPU spike when the search starts, and then it comes down to normal, and then Xcode hangs (appears as Not Responding) until it finally times out or something.
Other projects are fine. Search proceeds normally. And this only started in the last few weeks.
What I'm really worried about is a hard drive problem, but this seems very localized, and Disk Utility thinks my drive is fine.
I guess I can try making a copy of my project and searching the copy.
Has anyone seen anything like this before?!
Screenshot: Find gets stuck...
Rebuilding the code sense index didn't work either.
I did solve the problem though. The problem was a single file in my project - it seemed to be corrupt or damaged in some way. It couldn't be copied (which is how I discovered the culprit). It also couldn't be 'quick looked' or examined.
All I had to do was delete the damaged file, and revert it from my source control. And problem solved.
Now, how did it get damaged? I have no idea.