altrisi

From what I can see, I don't think this issue has anything to do with MCL-23025. This isn't an arbitrary file failing to download, it's a specific file (the game jar) that the launcher consistently tries to download from the wrong URL (it's not failing to! It's doing it but getting a 403 page from AWS therefore "failing"!) when using the `jar` attribute in the version JSON.

Let me know if I missed something in the other report though.

To reproduce the issue you need (steps for testing with the provided example against 1.17.1, but it should work the same for other versions. All paths are relative to the launcher directory, .minecraft):

• To not have the 1.17.1 jar file in the /versions/1.17.1/ folder:

  • Therefore go to the /versions/1.17.1/ folder and remove the 1.17.1.jar file if it's there

• To add a new folder inside /versions/ for a new version type with only the JSON like the one above (that has the jar attribute set to get it from 1.17.1, the version we don't have a jar from yet)

  • For the example, create a new folder inside /versions/ called 1.17.1-Test. Then drop the 1.17.1-Test.json file inside it

  • Do not put any JARs files in there, the idea (according to the JSON) is that the launcher should get the JAR from the /versions/1.17.1/ folder (once available, it's not there currently)

• Open the launcher now, go to Installations and make sure the Modded checkbox is enabled

• Create a new installation and set it to use your new version 1.17.1-Test. It may take a while to find it, given it'll be mixed inside a lot of versions, but it should be there unless the launcher was running when you created it

• Give any name to your installation and hit the Play button for it, wait for it to finish preparing

  • You'll need to acknowledge "modded" risks

• Now you'll be greeted with an error about unable to download the 1.17.1 JAR from the S3 URL in the report

That is the issue. The JSONs shouldn't change at all.

Now, if the JAR was already in there, the game is launched correctly. You can test that by launching 1.17.1 once first and then trying to launch our custom profile again. In that case it'll work correctly.

Let me know if you want me to record a more detailed video on how to reproduce the issue, I'd love to help get this fixed.

Can reproduce on 2.3.240 (latest update my device has received on stable).

This time I tried with 1.17.

There's one difference, now it no longer saves the invalid response, but still errors with the same message about trying to get it from AWS. The output window no longer contains anything other than a red (FATAL) empty line and "TIMER: Downloads took 0 seconds.". The error is instead in the failed to launch popup.

Image:

Could reproduce it in the latest release that my device received (10.0 2.2.12145).

Here's a video in how I did it:

As mentioned, if you've ran the regular 1.17.1 profile before (and therefore have the jar already downloaded), the issue doesn't happen.

A way to solve this seems to be (yarn names) implementing `canAvoidTraps()` from `Entity` to return `isMarker()`.

This is intended, you are using an Activator Rail instead of a Powered one. The activator rail will eject entities from the minecart.