* feat(INJI-267): add and export deviceId constant in constants file Use react-native-device-info library to get the unique identifier for each and every device * refactor(INJI-267): extracts AppId global variable into a global variable file and renames it to __AppId * refactor(INJI-267): extracts inji version and tuvali version handling into global variable file * feat(INJI-267): add telemetry configuration in the application * feat(INJI-267): generate unique session id for every session of the app After launching the app until we kill the app we consider it as a single session * feat(INJI-267): add start and end telemetry events for the QR login success flow * feat(INJI-267): pass session id value in sunbird config * feat(INJI-267): add start and end telemetry events for the VC sharing success flow * feat(INJI-267): add start and end telemetry events for the VC activation success flow * refactor(INJI-267): change QR login, VC share telemetry events type * refactor(INJI-267): extract generateSessionId function, deviceId into global variables file * feat(INJI-267): adds device related information in the config value * feat(INJI-267): add and export deviceId constant in constants file Use react-native-device-info library to get the unique identifier for each and every device * refactor(INJI-267): extracts AppId global variable into a global variable file and renames it to __AppId * refactor(INJI-267): extracts inji version and tuvali version handling into global variable file * feat(INJI-267): add telemetry configuration in the application * feat(INJI-267): generate unique session id for every session of the app After launching the app until we kill the app we consider it as a single session * feat(INJI-267): add start and end telemetry events for the QR login success flow * feat(INJI-267): pass session id value in sunbird config * feat(INJI-267): add start and end telemetry events for the VC sharing success flow * feat(INJI-267): add start and end telemetry events for the VC activation success flow * refactor(INJI-267): change QR login, VC share telemetry events type * refactor(INJI-267): extract generateSessionId function, deviceId into global variables file * feat(INJI-267): adds device related information in the config value * feat(INJI-267): add selected language in global variables file to pass it into sunbird config * feat(INJI-267): updates config structure and add AppInfo event * feat(INJI-267): create dummy end event data to make the schema and send AppInfo Event on app launch * feat(INJI-267): add and export deviceId constant in constants file Use react-native-device-info library to get the unique identifier for each and every device * refactor(INJI-267): extracts AppId global variable into a global variable file and renames it to __AppId * refactor(INJI-267): extracts inji version and tuvali version handling into global variable file * feat(INJI-267): add telemetry configuration in the application * feat(INJI-267): generate unique session id for every session of the app After launching the app until we kill the app we consider it as a single session * feat(INJI-267): add start and end telemetry events for the QR login success flow * feat(INJI-267): pass session id value in sunbird config * feat(INJI-267): add start and end telemetry events for the VC sharing success flow * feat(INJI-267): add start and end telemetry events for the VC activation success flow * refactor(INJI-267): change QR login, VC share telemetry events type * refactor(INJI-267): extract generateSessionId function, deviceId into global variables file * feat(INJI-267): adds device related information in the config value * feat(INJI-267): add and export deviceId constant in constants file Use react-native-device-info library to get the unique identifier for each and every device * feat(INJI-267): add telemetry configuration in the application * feat(INJI-267): pass session id value in sunbird config * refactor(INJI-267): change QR login, VC share telemetry events type * refactor(INJI-267): extract generateSessionId function, deviceId into global variables file * feat(INJI-267): adds device related information in the config value * feat(INJI-267): add selected language in global variables file to pass it into sunbird config * feat(INJI-267): updates config structure and add AppInfo event * feat(INJI-267): create dummy end event data to make the schema and send AppInfo Event on app launch * feat(INJI-267): bump up react-native-localize and remove unnecessary code * feat(INJI-267): remove some unused imports and unnecessary formattings * feat(INJI-267): remove unnecessary formattings * feat(INJI-267): extracts obsrv host in an env variable * feat(INJI-267): add env variable in react-native-dot-env index file * feat(INJI-267): bump up react-native-localize --------- Signed-off-by: Swati Goel <meet2swati@gmail.com> Co-authored-by: PuBHARGAVI <46226958+PuBHARGAVI@users.noreply.github.com> Co-authored-by: Swati Goel <meet2swati@gmail.com>
inji
MOSIP citizen app.
Dependencies
Be sure to have the following build tools installed before proceeding:
Generate keystore for APK signing
# Generate and use Debug keystore for development and testing purposes
keytool \
-genkey -v \
-storetype PKCS12 \
-keyalg RSA \
-keysize 2048 \
-validity 10000 \
-storepass 'android' \
-keypass 'android' \
-alias androiddebugkey \
-keystore android/app/debug.keystore \
-dname "CN=io.mosip.residentapp,OU=,O=,L=,S=,C=US"
# Generate and use Release keystore for Publishing to Play store
keytool \
-genkey -v \
-storetype PKCS12 \
-keyalg RSA \
-keysize 2048 \
-validity 10000 \
-storepass '<USE-YOUR-RELEASE-PASSWORD-HERE>' \
-keypass '<USE-YOUR-RELEASE-PASSWORD-HERE>' \
-alias androidreleasekey \
-keystore android/app/release.keystore \
-dname "CN=io.mosip.residentapp,OU=,O=,L=,S=,C=US"
Running the app
Prepare environment
Create a .env.local file using .env as your template:
MIMOTO_HOST=
GOOGLE_NEARBY_MESSAGES_API_KEY=
And android/local.properties:
GOOGLE_NEARBY_MESSAGES_API_KEY=
More info here: Setup Google Nearby Messages in React
Android
# install all dependencies
npm install
# run Inji Newlogic directly to connected emulator or device (Default)
npm run android:newlogic
# run Inji Mosip directly to connected emulator or device
npm run android:mosip
# run Inji Philippines directly to connected emulator or device
npm run android:ph
iOS
# install all dependencies
npm install
npx pod-install
# run Metro bundler in the background
npm start
# run Inji app directly to a connected device
npm run ios -- --device
Developing Android
Build via Android Studio
The app is available in this repository's frontend/android directory. Open this directory in Android Studio (version 4.1 and above) and the app can be built and run from there.
More info here: Build your app using Android Studio
Build via command line
You need Android SDK CLI to build APK.
# 1. Install dependencies
npm install
# 2. Setup the environment variables for the keystore
# Debug keystore
export DEBUG_KEYSTORE_ALIAS=androiddebugkey
export DEBUG_KEYSTORE_PASSWORD=android
# Release keystore
export RELEASE_KEYSTORE_ALIAS=androidreleasekey
export RELEASE_KEYSTORE_PASSWORD=<USE-YOUR-RELEASE-PASSWORD-HERE>
# https://hostname/residentmobileapp is the Mimoto service url
export BACKEND_SERVICE_URL=https://hostname/residentmobileapp
# Use one of following command to build the flavor you need.
# Build for Mosip Philippines test
npm run build:android:ph
# Build for Newlogic test
npm run build:android:newlogic
# Build for MOSIP test
npm run build:android:mosip
More info here: Build your app from the command line
Developing iOS
Build for TestFlight
- Install all dependencies
npm installnpx pod-install
- Open the
ios/directory in XCode - Set the build target to "Any iOS device (arm64)"
- Use an Apple Developer account that can provision builds for release/TestFlight
-
Don't forget to bump the version number when creating an archive
-
Open the Product menu and from there click Archive
-
Once done you can follow the dialog wizard to distribute the app to TestFlight
- Go to your App Store Connect dashboard to manage the newly-uploaded build.
More info here:
- React Native - Publishing to the App Store
- Apple Developer - Distributing Your App for Beta Testing and Releases
View the complete DB :
- Connect your phone to the laptop and open Android Studio.
- On the bottom right vertical tab you will find a
Device File Explorerbutton. Click on it and select you phone. - Navigate to
data -> data -> io.mosip.residentapp ->databases. You will find a file namedRKStoragein it. Download it. - Download DB Browser for SQLite .
- Open the file in this application. Click on
Browse Databutton and selectcatalystLocalStoragetable. Now you should be able to view the entire DB of Inji.
Credits
Credits listed here
Congratulations! 🎉
You've successfully run and modified your React Native App. 🥳
Now what?
- If you want to add this new React Native code to an existing application, check out the Integration guide.
- If you're curious to learn more about React Native, check out the Introduction to React Native.
Troubleshooting
If you can't get this to work, see the Troubleshooting page.
Learn More
To learn more about React Native, take a look at the following resources:
- React Native Website - learn more about React Native.
- Getting Started - an overview of React Native and how setup your environment.
- Learn the Basics - a guided tour of the React Native basics.
- Blog - read the latest official React Native Blog posts.
@facebook/react-native- the Open Source; GitHub repository for React Native.

