This page contains some common technical problems encountered by students and possible solutions.

iP

Troubleshooting Ui.png is not green in the dashboard even after I've added it to the repo.

Possible solution(s):

  • Ensure you've named it exactly as Ui.png (case-sensitive) and put it in the expected folder.
  • If you changed the case of your local file, ensure the file in your remote repo has the same name upper/lower case as the local file. Git does not propagate case changes in file names through pushes. You'll need to do some extra Git actions to propagate the case change to the remote repo.
    e.g., Although you changed UI.png to Ui.png in your local file, the remote repo's copy will remain UI.png even after you push changes to the remote repo.
  • Ensure you have published your iP website using GitHub pages, and the screenshot appears in the iP Showcase page.

Troubleshooting Markdown tables render correctly in GitHub file preview but not in the iP website.

Possible solution(s):

Ensure there is a blank line separates the table from the content just above it. This is a requirement of the Markdown syntax -- the Markdown parser used by GitHub's file preview forgives violations of this rule but not the parser used by the website renderer.


Troubleshooting My JAR file works on my OS, but not other OSes

Possible solution(s):

Ensure your build.gradle specifies JavaFX dependencies for all three OSes, as specified in our JavaFX tutorials.


Troubleshooting Error when running JAR file: JavaFX runtime components are missing

Possible solution(s):

Ensure your build.gradle specify the Launcher class as the mainClass.

application {
    mainClass.set("myduke.Launcher")
}

Troubleshooting Error when running JAR file: Error initializing QuantumRenderer: no suitable pipeline found

Possible solution(s):

Ensure you used the exact Java version we prescribe to build the JAR file, especially if you are on macOS.


Troubleshooting Error when running JAR file: ... compiled by a more recent version of the Java Runtime

Possible solution(s):

Ensure you used the exact Java version we prescribe to build the JAR file.