We notice recently after using the latest Aspose jar that when we set the license we get the below errors.
java.lang.NullPointerException: null
at com.aspose.slides.internal.oh.return.for(Unknown Source) ~[aspose-slides-22.9-jdk16.jar:22.9]
at com.aspose.slides.internal.oh.return.do(Unknown Source) ~[aspose-slides-22.9-jdk16.jar:22.9]
at com.aspose.slides.License.setLicense(Unknown Source) ~[aspose-slides-22.9-jdk16.jar:22.9]
another example
java.lang.NullPointerException: null
at com.aspose.diagram.vs.f(Unknown Source) ~[aspose-diagram-22.9.jar:22.9.0.0]
at com.aspose.diagram.vs.a(Unknown Source) ~[aspose-diagram-22.9.jar:22.9.0.0]
at com.aspose.diagram.License.setLicense(Unknown Source) ~[aspose-diagram-22.9.jar:22.9.0.0]
@aabuhijleh,
Thank you for the license file. Your license works fine on my end. Please check the problem using a new empty project. It looks like the error is related to your app. If the issue persists, please share more information to help us reproduce the exception (OS version, JDK version, etc.).
About Aspose.Diagram, can you please make sure that you are defining the dependency in pom.xml correctly? You do not have to include <classifier>jdk16</classifier> in pom.xml while declaring dependency.
We have logged an investigation ticket as DIAGRAMJAVA-51045 in our issue tracking system for further analysis. We will look into its details and let you know as soon as we resolve the ticket. Please be patient and spare us some time.
@aabuhijleh,
Thank you for the additional information. I’ve added a ticket with ID SLIDESJAVA-38935 to our issue tracking system. Our development team will investigate the case. We will inform you of any progress.
@aabuhijleh,
Unfortunately, our developers were unable to reproduce the error you are experiencing. Please share the following additional data and information:
We were unable to reproduce the issue for Aspose.Diagram for Java as well. Can you please provide your license file in a private message? image.png (10.8 KB)
Also, is it happening in multi-threading environment? Can you please isolate the license settings code and test again. Please give a try with 22.10 version of the API and let us know about the results you have.