Please refer to the sections below for more detailed information. The instructions assume the work is performed from a command line.
Please note – these setup instructions only apply to Intel-based machines. M1-based Mac support is coming, but isn't yet supported by our tooling.
- Download and install Xcode. WordPress for iOS requires Xcode 11.2.1 or newer.
- From a command line, run
git clone [email protected]:wordpress-mobile/WordPress-iOS.gitin the folder of your preference. - Now, run
cd WordPress-iOSto enter the working directory.
- Create a WordPress.com account at https://wordpress.com/start/user (if you don't already have one).
- Create an application at https://developer.wordpress.com/apps/.
- Set "Redirect URLs"=
https://localhostand "Type" =Nativeand click "Create" then "Update". - Copy the
Client IDandClient Secretfrom the OAuth Information.
- Check that your local version of Ruby matches the one in .ruby-version. We recommend installing a tool like rbenv so your system will always use the version defined in that file. Once installed, simply run
rbenv installin the repo to match the version. - Return to the command line and run
rake init:ossto configure your computer and WordPress app to be able to run and login to WordPress.com - Once completed, run
rake xcodeto open the project in Xcode.
If all went well you can now compile to your iOS device or simulator, and log into the WordPress app.
Note: You can only log in with the WordPress.com account that you used to create the WordPress application.
The steps above will help you configure the WordPress app to run and compile. But you may sometimes need to update or re-run specific parts of the initial setup (like updating the dependencies.) To see how to do that, please check out the steps below.
We use a few tools to help with development. Running rake dependencies will configure or update them for you.
WordPress for iOS uses CocoaPods to manage third party libraries.
Third party libraries and resources managed by CocoaPods will be installed by the rake dependencies command above.
We use SwiftLint to enforce a common style for Swift code. The app should build and work without it, but if you plan to write code, you are encouraged to install it. No commit should have lint warnings or errors.
You can set up a Git pre-commit hook to run SwiftLint automatically when committing by running:
rake git:install_hooks
This is the recommended way to include SwiftLint in your workflow, as it catches lint issues locally before your code makes its way to Github.
Alternately, a SwiftLint scheme is exposed within the project; Xcode will show a warning if you don't have SwiftLint installed.
Finally, you can also run SwiftLint manually from the command line with:
rake lint
If your code has any style violations, you can try to automatically correct them by running:
rake lint:autocorrect
Otherwise you have to fix them manually.
Launch the workspace by running the following from the command line:
rake xcode
This will ensure any dependencies are ready before launching Xcode.
You can also open the project by double clicking on WordPress.xcworkspace file, or launching Xcode and choose File > Open and browse to WordPress.xcworkspace.
In order to login to WordPress.com with the app you need to create an account over at the WordPress.com Developer Portal.
After you create an account you can create an application on the WordPress.com applications manager.
When creating your application, select "Native client" for the application type. The applications manager currently requires a "redirect URL", but this isn't used for mobile apps. Just use "https://localhost".
Your new application will have an associated client ID and a client secret key. These are used to authenticate the API calls made by your application.
Next, run the command rake credentials:setup you will be prompted for your Client ID and your Client Secret. Once added you will be able to log into the WordPress app
Remember the only WordPress.com account you will be able to login in with is the one used to create your client ID and client secret.
Read more about OAuth2 and the WordPress.com REST endpoint.
Read our Contributing Guide to learn about reporting issues, contributing code, and more ways to contribute.
If you happen to find a security vulnerability, we would appreciate you letting us know at https://hackerone.com/automattic and allowing us to respond before disclosing the issue publicly.
If you have questions about getting setup or just want to say hi, join the WordPress Slack and drop a message on the #mobile channel.
- The docs contain information about our development practices.
- WordPress Mobile Blog
- WordPress Mobile Handbook
WordPress for iOS is an Open Source project covered by the GNU General Public License version 2.