Inrupt Data Wallet

This project produces a mobile React Native application for use with the Inrupt Data Wallet service. This README provides information on:

• Setup and configuration
  • Prerequisites
  • Install dependencies
  • Configure build environment
    • Create keystore for Android
    • Make the keystore available to CI
• Running the application locally
  • On a device with Expo Go
  • On an Android emulator
  • On an iOS simulator
• Build the app on EAS
• Testing with Detox
  • On Android
  • On iOS
• UI overview
  • Home
  • Profile
  • Requests
  • Access
• Issues & Help
  • Bugs and Feature Requests
  • Documentation
  • Changelog
  • License

Setup and configuration

Prerequisites

In order to log into the Wallet, and for it to be able to persist data, you will need a Podspaces Account. Ensure that you have the following dependencies installed and configured:

On the mobile device

• Expo Go - app to be installed on a real device (iOS and Android supported)

On the dev machine (iOS)

If you are only running the app in Expo Go:

• NodeJS and NPM

If you are building the app locally, you'll also need:

• Xcode
• iOS simulators

On the dev machine (Android)

If you are only running the app in Expo Go:

• NodeJS and NPM

If you are building the app locally, you'll also need:

• A Java JDK
• Android emulators

Install dependencies

First, install all the project dependencies.

npm ci

Configure build environment

Copy the .env.sample file to .env and fill in any relevant values.

If you are testing manually, the minimal configuration is the URLs for the wallet's backend service.

EXPO_PUBLIC_LOGIN_URL=
EXPO_PUBLIC_WALLET_API=

Automated testing also requires access credentials for the Data Wallet:

TEST_ACCOUNT_USERNAME=<Wallet username>
TEST_ACCOUNT_PASSWORD=<Wallet password>

For testing with iOS simulators, you will need:

IOS_BINARY_PATH=<Path to the built iOS binary>
TEST_IOS_SIM=<Name of the iOS simulator on your device>

For testing with Android emulators, you will need:

ANDROID_BINARY_PATH=<Path to the main Android binary>
ANDROID_TEST_BINARY_PATH=<Path to the test Android binary>
TEST_ANDROID_EMU=<Name of the Android emulator on your device>

Ensure that the TEST_ANDROID_EMU configuration aligns with a device emulator in Android Studio. For example: TEST_ANDROID_EMU=Android_34. If the emulated device is called "Test Emulator 33", the EMU name will be Test_Emulator_33.

Create keystore for Android

The Android app will need to be signed for it to be installed. See: https://reactnative.dev/docs/signed-apk-android for more information on this.

WARNING: The following is only to be used for development. In production the keystore should be generated and configured in a more secure manner.

To generate a keystore with a key and cert run the following from the root of the project (this requires a Java JDK installation):

keytool -genkeypair -v -storetype PKCS12 \
 -keystore android/app/wallet.keystore \
 -alias wallet -keyalg RSA -keysize 2048 -validity 100 \
 -noprompt -dname "CN=wallet.example.com"

Add the following to: .env and update the placeholders.

KEYSTORE_PATH=<path>/inrupt-data-wallet/android/app/wallet.keystore
KEYSTORE_PASSWORD=<keystore password>

Running the application locally

Start the application:

npx expo start

In the output, you'll find options to open the app in a

• Expo Go, a limited sandbox for trying out app development with Expo.
• Development build
• Android emulator
• iOS simulator

On a device with Expo Go

After expo has started, make sure it targets the Expo Go environment (as opposed to "development build"). This will display a QR code which you will need to scan with your device.

The Wallet application will then build and install into your device for you to test & debug.

On an Android emulator

For Android, ensure that a virtual device has been added to the Android emulator by opening the new Device Manager with the following actions:

• Go to the Android Studio Welcome screen
• Select More Actions > Virtual Device Manager.

npm run android

Note: When running on the android emulator, there is a special loopback IP, 10.0.2.2, which points to the host machine 127.0.0.1. You can use it if the emulator complains about cleartext communication to the local network IP of the host.

On an iOS simulator

To build the iOS wallet app in an iOS simulator, run the following command:

npm run ios

This will install the necessary CocoaPods and compile the application. Upon completion, the iOS simulator should be open and the wallet app running.

Build the app on the Expo Application Service (EAS)

Prerequisite: All the following instructions are only applicable if you have an EAS account. By default, the project is configured to be built on an Inrupt EAS project. In order to build a custom version in your own EAS account, you'll need to create a new EAS project, and make sure that EAS project and the data (e.g. name, slug, project-id...) in your copy of app.config.ts are aligned.

Both the Android and the iOS versions of the app can be built using EAS. To do so, follow the instructions from the EAS documentation to setup your environment.

By default, the EAS CLI will trigger a build on the EAS infrastructure. It is also possible to run a build locally, which results in the built binary being available on the developer machine. This requires all the environment setup for being able to build the app locally, similar to npx expo run:<android | ios>.

The project ID is not hard-coded in the app.config.ts, but provided as an environment variable instead. In order to trigger an EAS build, please add the appropriate project ID in your environment variables, e.g.

EAS_PROJECT_ID="..." eas build --platform android --local --profile preview

Testing with Detox

On Android

Run the following command to build the Android app. This process may take up to 30 minutes to complete.

npx detox build --configuration=android.emu.release

For local development (a back-end server running on localhost or at an alternative location), use the android.emu.debug configuration. If running the debug configuration, make sure to run the development server (npx expo start).

Once built, run the detox tests for the relevant configuration:

npx detox test --configuration=android.emu.release

After completion, the binary apps will be located in:

./android/app/build/outputs

You can share the .apk files with others who need to run the Detox tests without building the Android app locally.

On iOS

If you want to generate the iOS binary, run the following commands. Note that this process may take around 30 minutes to complete.

xcodebuild -workspace ios/inruptwalletfrontend.xcworkspace -scheme inruptwalletfrontend -configuration Release -sdk iphonesimulator -derivedDataPath ios/build

After completion, the iOS binary should be located at:

inrupt-data-wallet/ios/build/Build/Products/inruptwalletfrontend.app

You can share the .app file with others who need to run the Detox tests without building the iOS app locally.

Execute the command below to start Detox test on iOS.

npx detox test --configuration=ios.sim.release

UI overview

Upon execution, the application prompts the user to log in. After successful authentication, the wallet app presents various views, located in the app/(tabs) directory:

• Home
• Profile
• Requests
• Access

Home

This page allows users to see all their assets within the wallet.

For each item, users can share it via QR code, download it, or delete it. Additionally, users can add new items: they can upload an existing photo, take a new one using the camera, upload an existing file, or use the QR scanner to request access to one.

Profile

This page displays the profile information of the wallet owner.

Here, users can see their webId and profile picture, if it is available. A QR code is also provided which can be used to share the user's wallet. Additionally, users can log out from this page.

Requests

This page displays the access requests for items within the wallet or for the wallet itself.

From here, the user can view all the requests along with their details (requestor, access mode, resource, and expiry date) and either confirm or deny access. If the user confirms the request, the requestor will be granted the specified access mode to the resource.

Access

This page shows what access has been granted to other agents.

For each authorized agent, there is a list of the wallet resources to which they have access. Users also have the option to revoke access to each resource from this page.

Issues & Help

Bugs and Feature Requests

• For public feedback, bug reports, and feature requests please file an issue via Github.
• For non-public feedback or support inquiries please use the Inrupt Service Desk.

Documentation

• Inrupt Data Wallet
• Homepage

Changelog

See the release notes.

License

Apache 2.0 © Inrupt