I was just launching my app on an avd and this weird "Failed to parse" error is occurring again and again. This is what is popping up:
Caused by: org.gradle.workers.internal.DefaultWorkerExecutor$WorkExecutionException: A failure occurred while executing com.android.build.gradle.internal.res.ParseLibraryResourcesTask$ParseResourcesRunnable
I tried to build the entire project again, but it gives the same output again and again. Can somebody help? Cheers :)
I have created an installer using install4j and uploaded. But sometimes if the download is not proper we get a corrupt installer (got to know by checking the file size) and it shows following error with error code 34.
Also found thee error to be:
[0:27] verifying integrity length 304907802
[2:157] ERROR: check ReadFile failed 0 0 187816324
I found that this is related to file size. But my question is how can we handle this in installer? As till this point we dont get control (ie.installer actions). I want to show custom error message on this issue.
Thanks in advance.
I have been researching on the topic for a couple of days and wrote a simple UNO component to work with the Spreadsheet. The main challenge I faced during the process is whenever the LO cannot find a class (i.e. some required jar is not included in the oxt package), the thread dies absolutely silently without throwing any exception. The only way to find out is to step trace all the suspecious code which is both frustrating and very time consuming. Only then can I see the exception message text and exception itself being created. Unfortunately, this exception is never really thrown in the environment I have or is silenced in some way.
Is there any way to enable LO to throw exceptions/see stack trace for debug purposes? Is there any location where LP puts java console output?
Any help is very much appreciated!
If you have not done so yet, I recommend getting the BookmarkInsertion example to work. Be sure that the application can find the main 4 jars in the classpath: juh.jar, jurt,jar, ridl,jar, unoil.jar.
Are you running the component from the Java IDE, for example, NetBeans?
Normally, build errors and exceptions are reported in the appropriate output window at the bottom of the IDE, and this is where java console output appears as well.
Otherwise, if you have already installed the OXT file in LibreOffice and are running it without a Java IDE, then there is no console output displayed. In that case, you may want to log to a file with something like log4j. However, error messages may still be able to pop up in a message box, depending on the error.
EDIT:
For an example in Eclipse, I followed the instructions at https://github.com/LibreOffice/loeclipse. To show messages:
Window -> Show View -> Console
Window -> Show View -> Error Log
When I renamed jurt.jar to jurt0.jar so that it cannot be found, then the following was shown in the Console pane.
Exception in thread "Thread-8" java.lang.ClassNotFoundException:
com.sun.star.comp.loader.JavaLoader
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
System.err.println also writes to the Console pane. I modified ActionOneDialog.java as follows.
public void show() {
System.err.println("show() BEGIN");
dialog.execute();
System.err.println("show() END");
}
Error below. Does anyone know why this is happening?
An error has occurred. See the log file /Users/Christian/Dropbox/Projects/Java Projects/.metadata/.log.
Log file:
(Was too big to post on SO, so here it is on gist:)
https://gist.github.com/4122659
I get a error on my JSP page:
Script error: "An error has occured in the script on the page"
When I try to run the Eclipse in the debug perspective and I am closing down the browser window of the eclipse where my application is running.
Because of the error the application hangs, and I am unable to test my application.
Is there any solution to this? I have to restart my eclipse again and again.
This would lead to corrupted files.
If you're lucky, the error message is caused by an Exception. In that case, you can add a Java Exception Breakpoint and the application should pause at the point where the script error is detected.