trouble running, cleaning or playing, starting play2.1 app. I can create the app, but then if i try to run, clean, play or start. i get this error
exception when typing play.Project.jdbc
class file needed by PlayReloader is missing.
any thoughts would be appreciated..
turned out to be a permissions issue. the app had lost its executable permission. no clue how it happened
Related
Please help me I am stuck due to below weird behavior of Intellij 2021.2.4(Ultimate Edition)
I am getting error after opening project in Intellij as below :
"Accessing invalid virtual file: file://; original:12323; found:12333; File.exists()=true.
I restarted my machine on weekend and then opened the Intellij Idea today morning .
I have tried below solutions but in vain
1.Invalid Caches
2.Remove idea64.exe.vmoptions
Thanks in advance .
I had this same issue just now. For me, I was running our app via JavaScript Debug task and the app would immediately fail; I'd get the error message in a "red balloon" above my Debug tool window tab.
Following the advice of #Andrey I checked the logs. Sure enough, there was a hint:
com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file:///Users/randy/projects/..../.../notifications; original:804838; found:805846; File.exists()=true
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.handleInvalidDirectory(VirtualDirectoryImpl.java:190)
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.doFindChild(VirtualDirectoryImpl.java:111)
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.findChild(VirtualDirectoryImpl.java:77)
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.findChild(VirtualDirectoryImpl.java:500)
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.findChild(VirtualDirectoryImpl.java:44)
at com.intellij.javascript.debugger.JavaScriptDebugProcess.isMeteorClientScript(JavaScriptDebugProcess.kt:587)
at com.intellij.javascript.debugger.JavaScriptDebugProcess.getLocationsForBreakpoint(JavaScriptDebugProcess.kt:538)
at com.intellij.javascript.debugger.JSLineBreakpointManagerBase.setBreakpoint(JSLineBreakpointManagerBase.kt:36)
at com.intellij.javascript.debugger.breakpoints.JSLineBreakpointHandler.registerBreakpoint(JSLineBreakpointHandler.kt:17)
at com.intellij.javascript.debugger.breakpoints.JSLineBreakpointHandler.registerBreakpoint(JSLineBreakpointHandler.kt:12)
IntelliJ was trying to register breakpoints when it crashed. From there, I simply opened the Breakpoints dialog and trashed everything since they were all recent and moot anyway.
After that, I just closed the debug browser window that was left from my last failed attempt, then reran the Debug config. Everything worked as expected.
For some reason, I am not able to start the same node-webkit application more than once. If I try to, I get the following error:
[37518:0100/000000:ERROR:zygote_linux.cc(546)] write: Broken pipe
Has anyone been able to do this? Thanks in advance
Solved my problem. Added
"single-instance": false
to the package.json file. Now I am able to start several instances of the same app.
This used to work for me, but now whenever I attempt to "Run in Simulator" with any of the iPhone or iPad types selected, I instantly get the console message
2013/10/1 10:4:48 Error: Script error. (URL: , LineNumber: 0)
I am working in the latest version of Chrome. Any help would be appreciated!
Just so that other users are aware, you can get that error on almost any problem in Mist and identifying the cause usually requires that we (I'm part of Icenium team) look into the specific project. In this particular case the problem was caused by missing App_Resources folder, which blaster has removed from his repository prior cloning it in Icenium. Generally an Icenium project should be able to function without this folder and we would fix this for the next version.
I'm trying to archive my app for submission, but I'm running into an error. In my app, I'm using the MBProgressHUD library, and the app works fine on the simulator, and all the devices I've tested on. However, when I go to Product > Archive, the build fails with the error saying:
MBProgressHUD/MBProgressHUD.h file not found."
Is there anything I had to do to prep the library? Any help would be appreciated, thanks!
~Carpetfizz
I just had to change the MBPogressHUD/MBProgressHUD.h to just "MBProgressHUD.h" in my files.
I just changed my sandboxed app's bundle identifier, and ran it. I get a runtime exception before main() even runs. The top of the stack trace is runtime_init. I tried running the app outside of Xcode and got the standard crash report dialog. Scrolling through the information presented, I noticed:
Application Specific Information:
dyld: launch, running initializers
/usr/lib/libSystem.B.dylib
xpchelper reply message validation: sandbox creation failed: 1002
Container object initialization failed: The operation couldn’t be completed. (Cocoa error 13.)
As soon as I run another time, there's no problem. I see that the container exists. As soon as I remove the container, though, the exception gets thrown again. I don't want my users' first experience with my app to be a crash. How can I fix this?
I tried repairing permissions, which made no difference. I also noticed that by the time Xcode breaks on the exception, the container has already been created. Also, Craig Hockenberry mentioned this error in a blog post, but he blamed symlinks in the user's Home directory. I don't have any symlinks there (not in the top level, at least, which is what I assume he means).
Additional input on Twitter suggests that it can be a symlink anywhere, in which case I definitely do have some. Has anyone discovered a workaround for it? I suppose that would be tough, as no application code executes before the exception. Hopefully Mountain Lion will fix it...?
Finally solved this crash by removing everything from the Desktop, Documents, Downloads, Movies, and Pictures user directories. I assume it's related to the sym link issue mentioned in other threads.