-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Update 1.14.10: Closes on startup #45
Comments
I have the same issue :( |
I've just noticed this behavior and unfortunately, I do not know what the issue may be. It could be something that Blitz/Electron has done to prevent tampering, because even with just extracting the 'app.asar' file without any changes to it causes the same behavior. Or maybe it could be something unrelated. There are no errors in the logs from what I can tell to help me find out the source of the problem. I can't promise any fix to the ad blocker anytime soon. I got a lot of other things to do so I don't got the time right now to dive deeper into this issue, and also because I currently have no leads on why this happening. If anyone is experienced in Electron apps, feel free to help out. |
Hello ! It's currently blocked, you can get Blitz to work again by reinstalling. I cleaned blitz-folders at %localappdata%/Programs and %appdata%. (Follow step 3 and 4 : https://support.blitz.gg/hc/en-us/articles/360033859312-Clean-Re-installation) I tried patching again without success. |
probably use pi-hole :) |
I have the same issue too |
Since the latest version of Blitz (1.14.15), I just got the message, the current version is not supported.
Does this belong to this issue too? |
The patch comparison failing means there were some lines of code changed (since 1.14.15) where the patcher modifies. This issue needs to be figured out before that could be fixed, because it will close on startup regardless if the patch comparison passes. (Patching is currently not working at all because any modifications to the Blitz client will close on startup) |
It appears this has stopped happening on the latest update. I have updated the release for the latest update. Closing this for now. |
Force closed on the new patch.
The text was updated successfully, but these errors were encountered: