Skip to content

Commit 0e05482

Browse files
authored
Merge pull request #20928 from wordpress-mobile/task/removed-wpcom-oauth-section
Replaces OAuth2 section with self-hosted test instructions
2 parents b7e59d3 + 01ab55f commit 0e05482

1 file changed

Lines changed: 7 additions & 33 deletions

File tree

README.md

Lines changed: 7 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -16,41 +16,8 @@ If you're a developer wanting to contribute, read on.
1616

1717
Notes:
1818

19-
* To use WordPress.com features (login to WordPress.com, access Reader and Stats, etc) you need a WordPress.com OAuth2 ID and secret. Please read the [OAuth2 Authentication](#oauth2-authentication) section.
2019
* While loading/building the app in Android Studio ignore the prompt to update the gradle plugin version as that will probably introduce build errors. On the other hand, feel free to update if you are planning to work on ensuring the compatibility of the newer version.
2120

22-
23-
## OAuth2 Authentication ##
24-
25-
In order to use WordPress.com functions you will need a client ID and
26-
a client secret key. These details will be used to authenticate your
27-
application and verify that the API calls being made are valid. You can
28-
create an application or view details for your existing applications with
29-
our [WordPress.com applications manager][5].
30-
31-
When creating your application, you should select "Native client" for the application type.
32-
The "**Website URL**", "**Redirect URLs**", and "**Javascript Origins**" fields are required but not used for
33-
the mobile apps. Just use "**[https://localhost](https://localhost)**".
34-
35-
Once you've created your application in the [applications manager][5], you'll
36-
need to edit the `./gradle.properties` file and change the
37-
`wp.oauth.app_id` and `wp.oauth.app_secret` fields. Then you can compile and
38-
run the app on a device or an emulator and try to login with a WordPress.com
39-
account. Note that authenticating to WordPress.com via Google is not supported
40-
in development builds of the app, only in the official release.
41-
42-
Note that credentials created with our [WordPress.com applications manager][5]
43-
allow login only and not signup. New accounts must be created using the [official app][1]
44-
or [on the web](https://wordpress.com/start). Login is restricted to the WordPress.com
45-
account with which the credentials were created. In other words, if the credentials
46-
were created with foo@email.com, you will only be able to login with foo@email.com.
47-
Using another account like bar@email.com will cause the `Client cannot use "password" grant_type` error.
48-
49-
For security reasons, some account-related actions aren't supported for development
50-
builds when using a WordPress.com account with 2-factor authentication enabled.
51-
52-
Read more about [OAuth2][6] and the [WordPress.com REST endpoint][7].
53-
5421
## Build and Test ##
5522

5623
To build, install, and test the project from the command line:
@@ -61,6 +28,13 @@ To build, install, and test the project from the command line:
6128
$ ./gradlew :WordPress:testWordPressVanillaDebugUnitTest # assemble, install and run unit tests
6229
$ ./gradlew :WordPress:connectedWordPressVanillaDebugAndroidTest # assemble, install and run Android tests
6330

31+
## Running the app ##
32+
33+
You can use your own WordPress site for developing and testing the app. If you don't have one, you can create a temporary test site for free at https://jurassic.ninja/.
34+
On the app start up screen, choose "Enter your existing site address" and enter the URL of your site and your credentials.
35+
36+
Note: Access to WordPress.com features is temporarily disabled in the development environment.
37+
6438
## Directory structure ##
6539
.
6640
├── libs # dependencies used to build debug variants

0 commit comments

Comments
 (0)