[CLIENT] "Incoming Network Connections" settings alerts repeatedly show up (Mac 10.10.1)

Upon every launch of the League of Legends client, two settings permission windows show up asking whether or not to accept incoming network connections for "LoLPatcher.app" and "LoLPatcherUx.app." This happens only when the system firewall is turned on.

Not tested on system versions other than Mac OS X 10.10.1 and the League of Legends client version 0.5.0.182.

Step-by-step instructions on how to reproduce the issue:

1. Boot up into Mac OS X 10.10.1.
2. If the League of Legends client was previously launched, make sure there are no permissions set to it in the system firewall settings. a) Open "System Preferences" and go to "Security & Privacy" b) Click on the "Firewall" tab. c) Click on the lock icon on the bottom of the window and provide the account password in order to unlock the firewall settings. d) If the firewall is off, click on the "Turn On Firewall" button. e) Click on the "Firewall Options" button. f) On the list of applications, look for "LolPatcherUx." If found, select it by left-clicking on it, and then click on the minus "-" sign located below the list. g) Click "OK" to save the changes and close the window. h) Close the "System Preferences" window by either hitting ⌘(command)+W or by clicking on the "x" button located on the top-left corner of the window.
3. Launch the League of Legends client.
4. Two system alerts show up asking for permissions to accept incoming network connections for "LoLPatcher.app" and "LoLPatcherUx.app" Screenshot
5. Click "Allow" for both of the alerts.
6. Close the client.
7. Following the instructions from step 2 above, "LolPatcherUx" application can now be found on the list of applications. Also, the status of it is set to "Allow incoming connections."
8. Again, launch the League of Legends client. The two systems alerts show up asking for permissions to accept incoming network connections for "LoLPatcher.app" and "LoLPatcherUx.app," clearly ignoring the firewall settings. Screenshot

The above steps reproduced the bug 3/3 times.