Since the upgrade to 1.4 Ive been having tonnes of issues. This is the latest, it builds, I can run the project, but if I make any changes it stays stuck here. I have to restart it to make it run. Any thoughts on what could be causing this?
Related
I've installed the latest version of meteor 1.4.2.3 and simply trying to create my first meteor app. The steps are simple but the process keeps looping on "Starting your app".
I've searched for solutions and tried the following with no success: meteor update, changing the port, npm install, meteor reset, uninstall and reinstall.
Stuck at "Starting you app" seems to be a common issue with no consensus on solution.
Please someone help!
Meteor needs quite a bit of memory, if you have less than 8GB it will struggle.
Sometimes just control-c it and starting it again works.
Sometimes it needs a
meteor reset
Another thing you can do is remove
<project-dir>/.meteor/local
Usually the problem only rears its head once in a while
I met this issue too. And Meteor stuck suddenly, it was working fine a day before. I tried everything. Uninstalling,reseting meteor, updating meteor, updating npm, meteor npm cache clean,Registry editing etc. Nothing helped. Then,
I updated my Windows 8.1 to Windows 10 and it was working again.
Edit: try this method first.
https://stackoverflow.com/a/46133529/3959840
I just downloaded meteor for Windows V 1.5.2. In my case I did not have Mongo DB installed.
I downloaded it from here and in cmd I set the MONGO_URL=' ' and boom it started my app.
Hope this helps someone :).
I've been using 1.1 on Win 10. When 1.2 came out, I tried upgrading but it actually falled back to 0.3. According to sashko a reinstall was necessary, which solved the problem for some. However, nothing happened when I uninstalled and rerun the installer. No files were actually modified. Deleting the %localappdata%/.meteor folder didn't help either. As the installer would no longer put anything there.
The farthest I could get is to get a dev build with a git clone, but I'd like to use a release version either 1.1 or 1.2. Otherwise I'm not able to update my project with a checkout meteor build.
Wrote a bunch of comments on other threads but none of the suggestions helped thus far, so I thought this deserves a new separate thread.
The solution was to clean the registry of meteor entries.
Credit goes to avalanche1 at: https://forums.meteor.com/t/windows-install-uninstall-hell/2375/7
Symptoms: Running any iOS 5.1 application from Xcode 4.4 (and 4.4.1) will launch the iPhone simulator but result in a plain black screen. In the Xcode console, the message "error: Failed to attach process to id " is displayed, being different each time. Attempting to 'Stop' the application from Xcode does nothing, and only Force Quit will return Xcode to a working state. Pressing the 'Home' button on the simulator shows that the app was successfully installed. Sometimes, opening the app from the simulator will show the UI, but no console messages are displayed, even after manually performing 'Product->Attach to process.'
Attempted Solutions: Xcode 4.3.x was originally installed on Lion, working charmingly. The problem started at installation of Xcode 4.4 in early August, for a project which was working before. I upgraded to Mountain Lion, didn't help. I reinstalled Xcode, didn't help. I upgraded to 4.4.1 Aug 7, didn't help. I deleted all trace of Xcode data, running: find / -name '[xX]code' and deleting all super-folders where it seemed relevant. That (not surprisingly) caused some OS issues, since subsequently reinstalling Xcode just didn't work. I then did it again, reinstalled Mountain Lion (to restore some OS files I probably killed), then reinstalled Xcode 4.4.1.
For projects, I typically ran new, single-view projects each time. Lately I've tried using this sample project from Apple, per link 3 below. I tried all the clean builds, etc., but honestly, one would assume opening a fresh project should just work. Just for kicks, I put a single 'Label' object in the iPhone storyboard at times.
After doing some homework I managed to find the following questions most similar to mine, but none are exact nor do any of the solutions work (in order of decreasing relevance):
xcode-4-4-ios-5-1-simulator-problems
crash-of-xcode-4-4-for-mac
failed-to-attach-to-process-id-xcode
unit-test-target-doesnt-run-on-xcode-4-5
xcode-4-4-freezing-on-project-close
simulator-keeps-crashing-in-xcode-4-4
Any help would be greatly appreciated. I apologize for the lack of brevity, but I've spent probably 15 hours trying to find/implement solutions to a seemingly trivial problem, and I would rather provide all relevant information than to have you guess at what I did. I'm not going to specify all the build info, just because it's whatever comes stock on the fresh install of Xcode.
I had similar problem (although with different configuration) and found incredibly simple solution by chance. I just used Product->Stop, then Product->Run (through keyboard shortcuts if that matters). Just once! Then the problem disappeared.
configuration: XCode 4.2, iPhone Simulator 5.0
symptom difference: process attaching didn't fail
It seems to me that the problem stems from the XCode-Simulator communication, and that's why I've shared my experience here despite the differences.
EDIT: It comes out Stop; Run didn't provide permanent solution for me. The problem is recurring from time to time. Still it is a temporary workaround for me.
I got this a few times, especially when I kept running my app and cancelling it or interrupting it too often, it's not something you can put your finger on, but yes I always managed to get back up and running by deleting the app in the simulator, cleaning project and build folder, deleting derived data (in Xcode organiser > projects view), restarting simulator and Xcode.
This also happened a few times on the device, and I needed to restart the device, iPhone in my case. I hope these infos help you out.
I got this to work by building and running the simulator using the Xcode 4.5 developer preview. I then closed it out and reopened Xcode 4.4.1 and it built and ran fine.
While none of the solutions above worked for me, thanks for putting this all together. I figured I'd answer here since this was the most comprehensive.
While this isn't exactly a solution, after today's OSX 10.8.1 update from Apple, this issue has been resolved. It's safe to say that some bug arose in the process of installing Mountain Lion and Xcode 4.4 that was fixed with this update to OSX.
I think I've cracked this one for my particular case, and I admit it's somewhat a mistake only newbies should do but I had overrided
viewWillApear:(bool)animated {}
in a ViewController of mine, without calling back
[super viewWillApear:animated]
It might be a good idea to search for all view lifecycle methods in your project and see if you have similar problem.
When I try to debug or run my flex application it shows "Out of memory" dialog.
I use IDEA 11.1 Ultimate and Windows 7 64x.
What I tried:
creating a new blank project and running it - same result (Out of
memory)
using 64x version of IDEA - didn't help
increasing xmx setting up to 6Gb - same result
installing IDEA 10.5 and launching my project there - it works fine. But I really need 11.1 to run my
project.
uninstalling and reinstalling JRE and JDK versions 7 and 6 (not at the same time ofc) -
didn't help
switching from flex SDK 4.6 to 4.5 - didn't help
reinstalling IDEA 11.1 with all the settings wiped out - didn't help!
It used to work fine before. I have no idea what could have changed.
I noticed that compilation works fine - I get a proper compiled swf file of my project that can be run in flashplayer. But right at the moment when IDEA is supposed to run the newly compiled swf it eats up all the memory.
What can be done about it? What else should I try?
I really don't understand why reinstalling IDEA didn't solve my problem. May be I didn't wipe out all settings?
Try File | Invalidate Caches or even run with all the defaults after renaming IDEA folders.
There were also some related fixes in IDEA 11.1.3 version, give it a try.
If it doesn't help, upload hprof memory dump to JetBrains FTP server and contact support for help, see http://devnet.jetbrains.net/docs/DOC-192 (Memory Snapshot section at the bottom) for details. You need to run IDEA with -XX:+HeapDumpOnOutOfMemoryError option.
Did you open more IDEA windows? Like opening another project into new window. In such case closing the other window will not release memory. The only thing that helps me is to restart the whole IDEA application.
I'm running XCode 4.0 I'm getting that error:
Xcode encountered an internal logic error. Choose "Continue" to continue running Xcode in an inconsistent state. Choose "Crash" to halt Xcode and file a bug with Crash Reporter. Choosing "Crash" will result in the loss of all unsaved data.
and also when i click on the show details button it gives me this:
ASSERTION FAILURE in /SourceCache/DVTFoundation/DVTFoundation-215/Framework/Classes/PlugInArchitectu re/DVTPlugInManager.m:215
Details: (extensionPoint) should not be nil.
Object: <DVTPlugInManager: 0x2000a3c20>
Method: -_extensionsForExtensionPoint:matchingPredicate:
Thread: <NSThread: 0x200020600>{name = (null), num = 1}
Hints: None
Backtrace: .............
I get this error if I try create a new file or modify any preferences, If I do just about anything. Could it be the actual project, it doesnt seem to happen with other projects.
It ran fine till I tried to add the Facebook IOS SDK to my project and then XCode "fell over". I have since removed the facebook SDK and still it happens I also opened a previous version of my app and still the same error.
I've tried clearing all the cache and still nothing works, is it worth downloading XCode 4.0.2 to resolve this or are there maybe other options. I'm in South Africa and 4 Gigs of data isn't for free.
I guess updating XCode to the latest version is always a good thing but is it that much better than 4.0? If there are other options to fix or find the problem, I would prefer it.
Thanks
I tried everything I've seen under this heading to stop xcode from crashing when debugging a simple C project. I even completely reinstalled Xcode4.
Finally tried this and it stopped the problem.
cd to the xcodeproj directory and:
rm -rf project.xcworkspace xcuserdata
I believe what I did that led up to the long series of crashes is set a watchpoint on a variable. I'm uncertain, but it was nearly the last significant thing I did before Xcode started puking on my shoes irrevocably.
I fixed the problem, although upgrading to 4.0.2 didn't do the trick, what I had to do is create a new project, and transfer all my files and change all my build settings after this it ran smoothly ever since. Hope this helps someone.
I had the same issue with a project stored in subversion.
I removed project.xcworkspace and xcuserdata from the xcodeproj directory and I also removed all .svn directories.
Building worked fine after.