Firefox for iOS

Download on the App Store.

This branch (main)

This branch works with Xcode 15.1, Swift 5.8 and supports iOS 17.2 and above.

Please make sure you aim your pull requests in the right direction.

For bug fixes and features for a specific release, use the version branch.

Getting involved

We encourage you to participate in this open source project. We love Pull Requests, Issue Reports, Feature Requests or any kind of positive contribution. Please read the Mozilla Community Participation Guidelines and our Contributing guidelines first.

You can file a new issue or research existing bugs

If more information is required or you have any questions then we suggest reaching out to us via:

Chat on Element channel #fx-ios for general discussion, or write DMs to specific teammates for questions.
Open a Github discussion which can be used for general questions.

Want to contribute on the codebase but don't know where to start? Here is a list of issues that are contributor friendly, but make sure to read the Contributing guidelines first.

Building the code

Install the latest Xcode developer tools from Apple.
Install, Brew, Node, and a Python3 virtualenv for localization scripts:
```
brew update
brew install node
pip3 install virtualenv
```

Clone the repository:

git clone https://github.com/mozilla-mobile/firefox-ios

Install Node.js dependencies, build user scripts and update content blocker:
```
cd firefox-ios
sh ./bootstrap.sh
```
Open the Client.xcodeproj under the firefox-ios folder in Xcode.
Make sure to select the Fennec scheme in Xcode.
Select the destination device you want to build on.
Run the app with Cmd + R or by pressing the build and run button.

⚠️ Important: In case you have dependencies issues with SPM, please try the following:

Xcode -> File -> Packages -> Reset Package Caches

Building User Scripts

User Scripts (JavaScript injected into the WKWebView) are compiled, concatenated, and minified using webpack. User Scripts to be aggregated are placed in the following directories:

/Client
|-- /Frontend
    |-- /UserContent
        |-- /UserScripts
            |-- /AllFrames
            |   |-- /AtDocumentEnd
            |   |-- /AtDocumentStart
            |-- /MainFrame
                |-- /AtDocumentEnd
                |-- /AtDocumentStart

This reduces the total possible number of User Scripts down to four. The compiled output from concatenating and minifying the User Scripts placed in these folders resides in /Client/Assets and are named accordingly:

AllFramesAtDocumentEnd.js
AllFramesAtDocumentStart.js
MainFrameAtDocumentEnd.js
MainFrameAtDocumentStart.js

To simplify the build process, these compiled files are checked-in to this repository. When adding or editing User Scripts, these files can be re-compiled with webpack manually. This requires Node.js to be installed, and all required npm packages can be installed by running npm install in the project's root directory. User Scripts can be compiled by running the following npm command in the root directory of the project:

npm run build

License