Forum Administrators KakerMix Posted March 2, 2012 Forum Administrators Posted March 2, 2012 Hi. We are aware of the issue and are working on a fix right now. It has everything to do with a certain 1.2 jar being changed from the one we were given before actual release. We are also working on a fix right now. Sorry for the wait guys! Issue is now resolved. Have a great day!
0 miniboxer Posted March 2, 2012 Posted March 2, 2012 Re: UPDATE FAILED ISSUE THANK YOU SO MUCH!! now i don't have to go around posting about it in every thread
0 miniboxer Posted March 2, 2012 Posted March 2, 2012 Re: UPDATE FAILED ISSUE once you get the current patch up and running, perhaps you could improve it so it can support unknown minecraft versions by using a code that uses this format: if minecraft ver = known, then chkMD5, else, then attempt backdate if chkMD5 < 1.1, then backdate, else, if, chkver == 1.1, then continue, else, then update
0 markyslayer Posted March 2, 2012 Posted March 2, 2012 Re: UPDATE FAILED ISSUE Please Hurry! I know you are doing everything you can, but i need to get on my friends server! Thank you
0 B Posted March 3, 2012 Posted March 3, 2012 Re: UPDATE FAILED ISSUE Is there an ETA for the fix? Or any temp. resolution? :'(
0 gugglle Posted March 3, 2012 Posted March 3, 2012 Re: UPDATE FAILED ISSUE Is there an ETA for the fix? Or any temp. resolution? :'( Well, you can manually downgrade your vanilla mc and install the mods yourself, or enjoy the 1.2 update while waiting.
0 TemporalWolf Posted March 3, 2012 Posted March 3, 2012 Re: UPDATE FAILED ISSUE It's interesting that even vanilla minecraft has a "Do you want to update?" option that technic apparently lacks. The launcher is unable to use backdated jars. It's the only mod I know that force updates (which will all but ensure it breaks after every update).
0 Forum Administrators KakerMix Posted March 3, 2012 Author Forum Administrators Posted March 3, 2012 Re: UPDATE FAILED ISSUE This issue is now fixed.
0 Ace1652 Posted March 3, 2012 Posted March 3, 2012 Hi. We are aware of the issue and are working on a fix right now. It has everything to do with a certain 1.2 jar being changed from the one we were given before actual release. We are also working on a fix right now. Sorry for the wait guys! Issue is now resolved. Have a great day! Actually I'm still having the same problem I chose both the recommended and developtment builds, and after pressing login and saying both yes and no to the update, it still says update failed! after backing up the previous build.
0 rhibakuska Posted March 3, 2012 Posted March 3, 2012 in my case, the SSP update works just fine, but when i tried to update vanilla, fails to update
0 agelian Posted March 3, 2012 Posted March 3, 2012 The issue was with the backdate code.. if the launcher doesnt have the patch to downgrade the mc jar then it will fail... And Minecraft managed to update to a new version 3 times in 2 days. There way to get around having to make a downgrade patch for each new version without distributing the jar yourself.
0 Ace1652 Posted March 3, 2012 Posted March 3, 2012 Hi. We are aware of the issue and are working on a fix right now. It has everything to do with a certain 1.2 jar being changed from the one we were given before actual release. We are also working on a fix right now. Sorry for the wait guys! Issue is now resolved. Have a great day! I downloaded a new launcher .exe and .jar and i deleted the .technicpack folder and it still prompts me an update and it still fails.
0 SpadgersHat Posted March 5, 2012 Posted March 5, 2012 I'm still getting 'update failed' when I try to log into Vanilla from the launcher. This happens both on online and offline mode. Running Technic Launcher 0.5.4.4 jar on a mac.
0 shaltac Posted March 5, 2012 Posted March 5, 2012 Thanks for all the work Kaker and team. Just wanted to mention that I was having the white screen / stuck at updating as of 7am. Deleting the launcher, and the ".t" folder, re-downloading the launcher, and re-installing fixed the issue. Thanks again Rusty Mod Note: Don't do this.
Question
KakerMix
Hi.
We are aware of the issue and are working on a fix right now. It has everything to do with a certain 1.2 jar being changed from the one we were given before actual release.
We are also working on a fix right now. Sorry for the wait guys!
Issue is now resolved. Have a great day!
13 answers to this question
Recommended Posts