Orchestration SDKs

Step 4. Running and testing the app

PingOne Advanced Identity Cloud PingAM React Native

In this step you build and run the sample app, then authenticate as a demo user using an authentication journey.

All commands should be run from the PingSampleApp directory unless otherwise specified.

Starting the Metro bundler

Metro is the JavaScript bundler for React Native.

Start it from the PingSampleApp folder in a terminal window, and leave it running:

cd PingSampleApp
yarn start

Running on Android

In a separate terminal window, make sure you are in the PingSampleApp folder, and run the sample app on an Android emulator or a connected device:

cd PingSampleApp
yarn android

Running on iOS

In a separate terminal window, make sure you are in the PingSampleApp folder, and run the app on the iOS simulator:

cd PingSampleApp
yarn ios

Xcode compiles the native layer and launches the simulator automatically. The first build takes several minutes.

Troubleshooting

How do I fix "Failed to build ios project. "xcodebuild" exited with error code '70'."?

This might be caused by the default simulator not being available as a destination for Xcode 26 from the command-line.

To work around this issue, close any open iPhone 17 simulators, and in the Simulator app, manually open an iPhone 15 or iPhone 16 simulator.

The sample app attempts to launch on a booted iOS device by default, but will start one if none are available. Leaving an iPhone 15 or 16 device running prevents the error code '70' issue in Xcode 26.

Authenticating with a journey

After launching the app, follow these steps to run an authentication journey:

  1. On the home screen, scroll to and tap settings Configuration under the SETUP section.

    1. On the Configuration page, select Journey Test Config, and then click the back arrow (arrow_back)

      Android sample app showing the Configuration page with Journey Test Config selected
      Figure 1. Selecting Journey Test Config on the Configuration page

  2. On the home screen, tap map Journey Flow under the AUTHENTICATION section.

    Android sample app home screen showing the Journey Flow option under the Authentication section
    Figure 2. Starting a Journey Flow from the home screen

  3. On the Journey screen, enter the name of an authentication journey, for example Login or sdkUsernamePasswordJourney, and then tap Start Journey.

  4. When prompted, sign in as your demo user:

    • Username: demo

    • Password: Ch4ng3it!

    Depending on the journey you ran, you might see a screen with a Logout and a Continue button.

    If this page appears, click the Continue button to complete the authentication journey.

    After successful authentication, the app displays user info:

    Android sample app showing user information after a successful authentication journey
    Figure 3. User info displayed after successful authentication

Viewing OAuth 2.0 tokens

  1. From the home screen, tap token Access Token under the USER MANAGEMENT section.

    1. On the Token screen, select the Journey tab, and then tap Access Token.

      The screen displays the access token and OAuth 2.0 user info retrieved from the server:

      Android sample app showing the access token and OAuth 2.0 user info on the Journey tab of the Token screen
      Figure 4. Access token and OAuth 2.0 user info on the Token screen

Signing out

  • From the home screen, tap logout Logout under the USER MANAGEMENT section.

    The app revokes the tokens on the server and clears them from secure storage on the device.

Next steps

You have successfully run the PingSampleApp and authenticated a user through a journey.

The app also provides screens to explore Device Management, OATH tokens, Push notifications, and more, all available from the home screen.

Try authenticating with a more complex authentication journey that includes MFA functionality such as device binding or OATH passcodes, then viewing and managing the registered authenticators in the device_hub Device Management page.