Skip to content
WordPress for iOS - Official repository
Swift Objective-C Ruby HTML Shell Python Other
Branch: develop
Clone or download

Latest commit

mindgraffiti Merge pull request #14171 from wordpress-mobile/issue/14170-site-addr…

UL&S: Enable the unified Site Address feature flag for local dev builds
Latest commit 2a78882 May 26, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Fix release builds configuration May 4, 2020
.configure-files Update configuration Nov 21, 2019
.github Disable broken Danger to avoid noise for the dev team May 16, 2020
Scripts Merge pull request #14107 from wordpress-mobile/update-code-freeze May 25, 2020
WordPress.xcworkspace Revert "Fixes for background on featured image in post settings" Jan 9, 2020
WordPress Merge branch 'develop' into issue/14170-site-address-ff May 26, 2020
WordPressFlux Update shared schemes to version 11.3 Mar 11, 2020
WordPressShared/WordPressShared/Core Merge branch 'develop' into feature/8954-stock-photos-update-mark-II Apr 20, 2018
config Bump version number May 19, 2020
docs Docs: Add info about why plurals are not supported. Feb 6, 2020
patches Patch RN to have a possibility to disable buttons in action sheet May 6, 2020
.clang-format Add clang format file. Mar 18, 2015
.configure Update configuration Nov 21, 2019
.gitattributes Add support for diffing .strings files Apr 12, 2019
.gitignore Set up Yarn to fetch Danger and TypeScript Feb 19, 2020
.hound.yml Corrected ruby key as well Sep 27, 2018
.ruby-version Upgrade to XCode 11.2 Nov 25, 2019
.swiftlint.yml Catch interpolation at the start of the string Nov 26, 2018
.xctool-args Fixed deployment target and xctool builds Nov 20, 2013 Updated Code of Conduct with contact information Feb 10, 2017 CODESTYLE: Change link to docs folder Oct 22, 2019 Update May 3, 2019
Gemfile Update fastlane and plugins May 12, 2020
Gemfile.lock Update to release-toolkit 0.9.4 May 25, 2020
LICENSE Project file cleanup Mar 27, 2014 Include post autosave identifier in core data Nov 29, 2019
Podfile Merge branch 'develop' into issue/14170-site-address-ff May 26, 2020
Podfile.lock Merge branch 'develop' into issue/14170-site-address-ff May 26, 2020 Clarificaitons based on PR review. Jan 23, 2020 Updated hot fix branch version to 9.1 Dec 22, 2017
RELEASE-NOTES.txt Merge branch 'develop' into feature/use_google_login_refactor May 22, 2020
Rakefile Update Rakefile Jan 29, 2020 Add responsible disclosure policy (#11666) Jun 3, 2019
package.json Set up Yarn to fetch Danger and TypeScript Feb 19, 2020
yarn.lock Bump minimist from 1.2.0 to 1.2.5 Mar 18, 2020

WordPress for iOS

CircleCI Reviewed by Hound

Build Instructions

Please refer to the sections below for more detailed information. The instructions assume the work is performed from a command line.

  1. Download and install Xcode. WordPress for iOS requires Xcode 11.2.1 or newer.
  2. From a command line, git clone in the folder of your preference.
  3. cd WordPress-iOS to enter the working directory.
  4. rake dependencies to install all dependencies required to run the project (this may take some time to complete).
  5. rake xcode to open the project in Xcode.
  6. Compile and run the app on a device or an simulator.

In order to login to using the app:

  1. Create a account at (if you don't already have one).
  2. Create an application at
  3. Set "Redirect URLs"= https://localhost and "Type" = Native and click "Create" then "Update".
  4. Copy the Client ID and Client Secret from the OAuth Information.
  5. From a command line, ensure you are in the project's working directory and run cp WordPress/Credentials/wpcom_app_credentials-example .configure-files/wpcom_app_credentials to copy the sample credentials file.
  6. Open the newly copied .configure-files/wpcom_app_credentials with the text editor of your choice, and replace WPCOM_APP_ID and WPCOM_APP_SECRET with the Client ID and Client Secret of the application you created. Note that .configure-files will be hidden by default in Finder. If you need to view it in Finder, hold down Control+Shift+. and it should appear.
  7. Recompile and run the app on a device or an simulator.

You can only log in with the account that you used to create the WordPress application.

Third party tools

We use a few tools to help with development. Running rake dependencies will configure 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.

Open Xcode

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.

Setup Credentials

In order to login to with the app you need to create an account over at the Developer Portal.

After you create an account you can create an application on the 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, create a credential file. Start by copying the sample credentials file in your local repo by doing this:

cp WordPress/Credentials/wpcom_app_credentials-example .configure-files/wpcom_app_credentials

Then edit the WordPress/Credentials/wpcom_app_credentials-example file and change the WPCOM_APP_ID and WPCOM_APP_SECRET fields to the values of your application's client ID and client secret.

Now you can compile and run the app on a simulator and log in with a account. Note that authenticating to via Google is not supported in development builds of the app, only in the official release.

Remember the only 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 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 and allowing us to respond before disclosing the issue publicly.

Getting in Touch

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.



WordPress for iOS is an Open Source project covered by the GNU General Public License version 2.

You can’t perform that action at this time.