-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem when trying to start Infinity evolved 1.7 #1202
Comments
Hay, thanks for the issue! Unfortunately it looks like you've not provided a Please do the followingUpload Logs using the appOpen the Settings page in the FTB App, then go to the app tab and click on the Either edit your original issue or add a comment with this code. Using the FTB Debug toolOnly use this method if asked to or if your app wont open fully/the above method doesn't work, you can use the FTB Debug tool to generate a code for you. Please use the link below to download and run the FTB Debug tool. This is a tool built by our App Developers and will provide you a code that you need to attach to this issue. Please either edit your original issue or add a comment with this code. If you need more help running this tool, you can follow our guide on how to use the FTB Debug tool. Windows // MacOS // Linux // Windows (Arm) // MacOS (Arm) // Linux (Arm) |
Here the debug code:) https://pste.ch/ivugukuqat |
If you go to the settings in the FTB App, you should see 3 buttons under common folders, click on the one named |
Thank you very much! Works well! Have a great day! ;) |
What Operating System
Windows 8.1
Debug Code
[21:13:30] [Instance Launcher 1/ERROR] [net.creeperhost.creeperlauncher.api.handlers.instances.LaunchInstanceHandler]: Failed to launch instance. net.creeperhost.creeperlauncher.pack.InstanceLaunchException: Failed to prepare instance 'FTB Infinity Evolved 1.7'(fdd1a662-540e-4e62-8b14-c3ef425b5f8b). at net.creeperhost.creeperlauncher.pack.InstanceLauncher.prepareProcess(InstanceLauncher.java:514) ~[launcher-c3a5d288d9-all.jar:?] at net.creeperhost.creeperlauncher.pack.InstanceLauncher.launch(InstanceLauncher.java:152) ~[launcher-c3a5d288d9-all.jar:?] at net.creeperhost.creeperlauncher.pack.Instance.play(Instance.java:416) ~[launcher-c3a5d288d9-all.jar:?] at net.creeperhost.creeperlauncher.api.handlers.instances.LaunchInstanceHandler.lambda$handle$0(LaunchInstanceHandler.java:56) ~[launcher-c3a5d288d9-all.jar:?] at java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source) ~[?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?] at java.lang.Thread.run(Unknown Source) ~[?:?] Caused by: java.lang.NullPointerException: Cannot invoke "com.google.gson.JsonElement.isJsonObject()" because "element" is null at net.covers1624.jdkutils.JdkInstallationManager$Installation.migrate(JdkInstallationManager.java:383) ~[launcher-c3a5d288d9-all.jar:?] at net.covers1624.jdkutils.JdkInstallationManager$Installation.access$000(JdkInstallationManager.java:366) ~[launcher-c3a5d288d9-all.jar:?] at net.covers1624.jdkutils.JdkInstallationManager.(JdkInstallationManager.java:66) ~[launcher-c3a5d288d9-all.jar:?] at net.creeperhost.creeperlauncher.Constants.getJdkManager(Constants.java:162) ~[launcher-c3a5d288d9-all.jar:c3a5d288d9] at net.creeperhost.creeperlauncher.pack.InstanceLauncher.prepareProcess(InstanceLauncher.java:334) ~[launcher-c3a5d288d9-all.jar:?] ... 7 more
Describe the bug
Idk... try to launch the game but 5 sec later there is: "unable to start pack... please see the instance log" and "failed to prepare instance 'FTB Infinity Evolved 1.7' (fdd1a662-540e-4e62-8b14-c3ef425b5f8b). because.. java.lang.NullPointerException: Cannot invoke "com.google.gson.JsonElement.isJsonObject()" because "element" is null
Steps to reproduce
like I mentioned above :(
Expected behaviour
I´m not the smartest when it comes to certain things. I just want to play the old FTB versions from older times. ;)
Screenshots
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: