PR Details

This PR sets up the Github Actions and automatic release when a PR is merged into the master branch

Description

• Added Fastlane to the project
• Create the Github workflow file
• Added the Gemfile to manage the dependencies
• Custom Fastlane Actions created

Motivation and Context

This is required in order for the project to have automatic releases

PR Details

• Bumping release version 1.5.0
• Fixing unzip of new mitmproxy version when user already has the app installed

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

PR Details

• Bumping release version 1.5.0
• Fixing unzip of new mitmproxy version when user already has the app installed

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

PR Details

• Fixed the usage of new mitmdump v2 location, the app was looking for the older version yet
• Fixed the execution of scripts when exiting the app, now they will be executed in sync mode to guarantee the expected result. This fixes a problem when you quit the app with proxy or server turned on and still keeps activated while not using mockingbird anymore.

Types of changes

• [ ] Docs change / refactoring / dependency upgrade
• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

PR Details

This adds a new feature to mockingbird where it will be able to update itself.

Description

• This adds the Sparkle framework to the project. This framework enables the app to auto update, which will improve the project user experience overall.

• Also, makes all the binding necessary to integrate the project with the Sparkle framework

• And finally, it adds the new AppCast file, which will be used in order to make the updates to the next versions possible.

Types of changes

• [ ] Docs change / refactoring / dependency upgrade
• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [X] My code follows the code style of this project.
• [X] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [X] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [X] All new and existing tests passed.

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

PR Details

Bumping release version 1.4.0

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

PR Details

• Updating the logo

Types of changes

• [x] Docs change / refactoring / dependency upgrade
• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

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 the mitmdump_mb file. The code we have today checks if the mitmproxy 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 to mitmproxy-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

• [ ] Docs change / refactoring / dependency upgrade
• [ X] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• X[ ] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ X] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

PR Details

• Bumping release version 1.3.0

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

PR Details

Up until now the mitmproxy was intercepting all network traffic which caused issues when trying to perform other network activities with Mockingbird activated.

With these changes, we'll leverage the --allow-hosts option to solely intercept requests with the path for the context selected. This will allow any user to use internet freely on their device when filtering requests according to their request

Description

• Adds mitm-on.sh script to start the mitmdump_mb executable with the --allow-hosts option depending on the selected context status
• Removes filtering performed on ContextManager (no longer needed since this is being done at the mitmproxy level
• Adds label to alert the user to disable the Server before changing the context
• Removes ProcessObject and runAsync since we're no longer launching executables directly from the source code

Motivation and Context

In our teams, a painpoint that we felt a lot was the loss of all network connection when we simply wanted to intercept requests based on a determined context.

How Has This Been Tested

After applying these changes, I ran the Mockingbird app several times with no context applied or with context applied (with single or multiple paths). While in the first scenario all traffic is targeted and any activity using internet traffic is halted, in the second scenario only the traffic that is targeted by the context is intercepted and the user can work with the remaining activities.

Types of changes

• [ ] Docs change / refactoring / dependency upgrade
• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [x] All new and existing tests passed.

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

PR Details

Correct behaviour for the "Open Data Folder" button on the settings screen after the changes made to the working directory

Description

When pressing the "Open Data Folder", Mockingbird now opens the working directory instead of its main directory as it was previously

Motivation and Context

Correct behaviour that was incorrect after the changes in 1.2.0

How Has This Been Tested

Ran the Mockingbird app and tested the behaviour before and after the changes

Types of changes

• [ ] Docs change / refactoring / dependency upgrade
• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement