When I try to start PhpStorm the little Windows 10 loading circle pops up for like one second. After that disappears just nothing happens. I get no error message or error log. PyCharm and IntelliJ is working fine.
Any ideas or experience?
Related
I am brand new to React-Native and have been consistently having major issues getting things up and running. I am using VS Code, Expo, Chrome, and Android Studio. I have encountered at least a dozen major issues trying to get a simple "Hello World" app running and none of the solutions to the particular problems has really worked leading me to believe there is a bigger issue going on. I'll try to run through a few of the issues I've had so far but as I said I'm totally new to this so I can't really understand/remember every issue that has come up.
I have consistently had issues getting metro bundler/expo and the Android Virtual Devices connecting. Sometimes they work, but most of the time I get the warning message "Couldn't adb reverse: device 'adb' not found" followed by the error message "Couldn't start project on Android: Error running adb: device 'adb' not found." If the device does work, if I try to reload from the developer menu or debug from the developer menu, expo crashes on the virtual device. Often I get a blank white screen and the developer menu will no longer open. I've had occasional success stopping the virtual device, restarting it, closing all expo windows, and trying to "run on android" from metro bundler. When this doesn't work, I've tried wiping the virtual device. Sometimes this works. Most often I have to delete the device and create a new one.
When I tried to run the debugger in Chrome, the times it appeared to work, I got console screens that didn't match any guides I've found online. Trying to force errors to understand the Chrome debugger completely crashed the virtual device. Had to close VS Code, Chrome, and delete the virtual device to be able to even begin again.
When I tried to follow guides to debug in VS Code I couldn't get that to work either. Regardless if I put in break points or not when I tried to run "attach to packager" it wouldn't output anything but I could hear my machine running really hard and VS Code seemed like it was trying to do something. I would have to close VS Code to get it working again. The other issue I would get an error telling me that Packager was running outside of VS Code. I would try to close down Android Studio and restart and I would get the same error. One time I almost got it working but the virtual device completely crashed and started flashing a white screen and had to be deleted.
I've had tons of other random errors that have only happened once or twice including some warning message about the binary of the android devices being obsolete or something like that.
Anyone have any idea what could be causing all of this? I've been dealing with this for almost two weeks and it has become incredibly frustrating.
I just upgraded my RubyMine to v8.0.0 with the custom bundled JDK. After installing it I tried to open the app from it's icon and nothing happened. I mean it showed me the dialog box if I trust the app (this happens whenever you want to open a new installed app for the first time), but afterwards nothing showed up.
I looked through the app processes, and couldn't find the RubyMine app. I also tried the solution from this question:
RubyMine fails to start on Yosemite
No success.
After I ran chmod +x /Applications/RubyMine.app/Contents/MacOS/rubymine, I tried again from the app icon, but it still doesn't seem to work.
I updated my java version to java version "1.8.0_65" and still no luck.
It works when I run /Applications/RubyMine.app/Contents/MacOS/rubymine from the command line.
Just to be clear, before upgrading to v8.0 this problem didn't occur.
I run OS X Yosemite.
Any ideas what can cause this issue?
[UPDATE] I ended up downgrading to v7.1.4 until this gets solved.
Found the problem. Looks like I had to run the app in 64-bit mode.
Right click app icon -> Get Info -> "Open in 32-bit mode" must be unchecked.
OS X 10.9.3 iMac
Installed Xcode 6 beta today and I am immediately stuck.
Following an apparently successful install, without errors, I have done nothing more than:
Clicked the "Xcode 6 Beta" icon to run
On the "Welcome to Xcode" screen, clic ked "Get started with a playground"
Created a new Playground file
Error thrown. "Error running playground. Failed to prepare for communication with playground"
All options under the "Product" menu are grayed out: Run, build, etc.
Anyone else, or is it just me?
Tyvm
Keith
I had the same problem. Try closing Playground or Xcode 6(Same thing) and reopen. This seemed to fix my problem.
Recently I updated my project settings as Xcode recommended. I just pressed a button and they did "everything". However now when I try to run my app on my device it freezes on the loading bar at about 75% and then after 15 seconds it says "build succeeded" but does not run on my device and everything stops as if I had pressed the stop button. I am getting no errors but I am getting the following warnings. It works on the simulator just fine.
For the record I have looked this up and everyone says to add "armv6 or armv7" and I already have this done. I am running deployment target iOS 3.0+
If anyone can help me, it would be appreciated. Thank you!
EDIT
Works on my device when I run leaks in instruments... but won't without instruments
Well, I can't really say much specific here, but if all else fails, I'd try making a new project and copying the content of this project to the new one. This could fix some underlying problems that may have developed in the build settings etc.
I have a long file inside intelliJ (java, properties, ruby) if I leave my caret on Line 1 and scroll down to line 300, then the caret keeps on scrolling down with my screen as i keep scrolling down. Is this a bug or a setting of IntelliJ?
I am scrolling down using my mouse, and then also using my TrackPad. This happens for me inside IntelliJ on Mac AND on ubuntu, so im guessing it's either a bug, or a feature.
It was the vim plugin that was causing this problem. Once I uninstalled it, everything began working.
I see the same problem in any application (also in Windows), but only with my laptop (Thinkpad). If I just touch the trackpad, it stops scrolling. Not a real solution, but just a workaround that has helped me a lot of times.
I also see the same problem in my IntelliJ Idea. I fixed it by enable Vim plugin - restart my Idea - disable Vim plugin. Then it fixed. Only disable Vim maybe not work. You can tray these 3 steps to active this change to let Idea know.