This is frustratingly, NOT resolved and has been simply swept under the rug and I doubt it was even attempted to be replicated. It is obviously a bug and NOT working as intended. After considerable time analyzing the issue here's why:
Grum says, "the firewall SHOULD block this", but actually the firewall should ALLOW traffic if the minecraft.app is listed in the allowed apps list.
No, this is NOT an Apple issue because when you first launch Minecraft with the firewall on the little prompt asking you if you would like to allow/deny a firewall connection appears and disappears so quickly you almost miss it if not paying attention. I suspect Minecraft is somehow causing this prompt not to stick around long enough for us to be able to respond and add the TRUE application or sub-application to our firewall list. I don't think it's intentional window-closing code, but perhaps the movement from the launcher to the actual .jar that is throwing off the prompt. Who knows, but THIS is the issue and is where the team needs to put a little bit of investigative attention. Just a little guys, c'mon. Just take a look here and replicate this behavior that doesn't allow us to approve the app for the firewall.
My point is that there IS something that can be done about this issue that many users are experiencing and something that can be done about the lack of security that they have to endure just to play the game on LAN (turning off the firewall for the entire OS). To say that this is "working as intended" is absolutely false. The firewall should NOT block Minecraft if it is specifically allowed.
I request that you re-open this very issue and put it on a bugs list even if at low priority. Don't down-play this because you have greater issues. I hope enough people experiencing this will speak up and make you realize that you have to do something about it if you don't want to alienate those desiring to play LAN on Mac.
Joseph Knight
This is frustratingly, NOT resolved and has been simply swept under the rug and I doubt it was even attempted to be replicated. It is obviously a bug and NOT working as intended. After considerable time analyzing the issue here's why:
Grum says, "the firewall SHOULD block this", but actually the firewall should ALLOW traffic if the minecraft.app is listed in the allowed apps list.
No, this is NOT an Apple issue because when you first launch Minecraft with the firewall on the little prompt asking you if you would like to allow/deny a firewall connection appears and disappears so quickly you almost miss it if not paying attention.
I suspect Minecraft is somehow causing this prompt not to stick around long enough for us to be able to respond and add the TRUE application or sub-application to our firewall list. I don't think it's intentional window-closing code, but perhaps the movement from the launcher to the actual .jar that is throwing off the prompt. Who knows, but THIS is the issue and is where the team needs to put a little bit of investigative attention. Just a little guys, c'mon. Just take a look here and replicate this behavior that doesn't allow us to approve the app for the firewall.
My point is that there IS something that can be done about this issue that many users are experiencing and something that can be done about the lack of security that they have to endure just to play the game on LAN (turning off the firewall for the entire OS). To say that this is "working as intended" is absolutely false. The firewall should NOT block Minecraft if it is specifically allowed.
I request that you re-open this very issue and put it on a bugs list even if at low priority. Don't down-play this because you have greater issues. I hope enough people experiencing this will speak up and make you realize that you have to do something about it if you don't want to alienate those desiring to play LAN on Mac.