macOS FTB Launcher "Failed to download file" for most modpacks

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

BigDrizzle

New Member
Aug 25, 2021
2
0
2
Launcher gives me this error when trying to download MOST recent modpacks.

Failed to download file. Name: 1.16.5-forge-36.2.2.jar URL: https://s3.amazonaws.com/Minecraft.Download/versions/1.16.5-forge-36.2.2/1.16.5-forge-36.2.2.jar Filename on disk: 1.16.5-forge-36.2.2.jar Path: /Users/xxx/Library/Application Support/.ftba/bin/versions/1.16.5-forge-36.2.2/1.16.5-forge-36.2.2.jar Exists: File

This file never downloads and then I obviously cannot launch the modpack. I tried manually downloading this file. Also tried transferring it from a windows machine where it is working, but I still cannot launch the game.

I tested this with Direwolf20, University and Academy. Same error (although trying to download a different jar in some cases) Oddly, FTB Endeavour does not have this error and is able to download to /Users/xxx/Library/Application Support/.ftba/bin/versions/ without issue.

Not sure what other logs are needed.

FTBapp: Version 0.1.0 (0.1.0.719)
macOS: 11.5.2
Launcher: 2.2.3964
 
Last edited:

Chanko

New Member
Aug 30, 2021
2
0
2
I am having this exact same issue. After I click play from the ftbapp (the same packs you mentioned), the minecraft launcher starts. I click play and it errors with the same as you stated. Click "play" again in minecraft launcher and it looks like it is downloaded but then the game launches and immediatly crashes with exit code 0. No other info unless someone can point me to the correct logs to check out.

I have tried to go through my machine and remove all instances of previous installs and all settings and configurations. But after reinstall of FTBApp it does the exact same thing.

Yesterday I was able to do a full fresh install on my daughters computer (never had mc installed on it) and she downloaded academy modpack and started playing right away. That makes me think that it is something lingering on my machine that is preventing it to work.
 

BigDrizzle

New Member
Aug 25, 2021
2
0
2
I am having this exact same issue. After I click play from the ftbapp (the same packs you mentioned), the minecraft launcher starts. I click play and it errors with the same as you stated. Click "play" again in minecraft launcher and it looks like it is downloaded but then the game launches and immediatly crashes with exit code 0. No other info unless someone can point me to the correct logs to check out.

I have tried to go through my machine and remove all instances of previous installs and all settings and configurations. But after reinstall of FTBApp it does the exact same thing.

Yesterday I was able to do a full fresh install on my daughters computer (never had mc installed on it) and she downloaded academy modpack and started playing right away. That makes me think that it is something lingering on my machine that is preventing it to work.
I dug pretty deep and could not root cause why that Jar refused to download or why I could not manually replace it.

I ended up just moving my server and client modpack version back 1 revision, to version to 1.10.1
 

Chanko

New Member
Aug 30, 2021
2
0
2
ok. I think I got it to work.

In the minecraft launcher, I created a new instance of 1.16.5. It downloaded and I launched it and it loaded vanilla up just fine. After that, I manually downloaded the forge installer. Run that and point to the .ftba/bin directory. Installed forge successfully. Reopened FTBapp and relaunched my modpack. Clicked play on minecraft launcher and all seems to be working now.