Changing the port to work on the MacOS Monterey #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Details
Changes the port from 5000 to 5999, to correct a bug that was preventing the server to start on the macOS Monterey
Description
When we were trying to connect to the server, this error was being shown:
The operation couldn’t be completed. (SwiftSocket.SocketError error 2.)
. On the macOS Monterey, the port 5000 is used by Control Center, to operate the Airplay Receiver, so this was preventing the Mockingbird server to connect. Changing it to 5999 fixed the problem.Also, we had to change the
mitmproxy
folder, due to the change we had to do on themitmdump_mb
file. The code we have today checks if themitmproxy
folder is empty and then we copy the file to it. This was preventing the file to be updated. So, we have found a temporary solution to overcome that, that is to change to name of the folder tomitmproxy-v2
.Also, the Swifter lib was updated to the 1.5.0 version.
Motivation and Context
This change is required to fix the function problem on the macOS Monterey
How Has This Been Tested
After fixing the problem, I ran the app several times and tested the intended behavior. Everything worked just fine
Types of changes
Checklist
Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement