This is an Android app. We have submitted the latest APK build of the app with the submission of our final project.

To access it:

1. Download the APK file on your mobile device
2. Install it on your Android mobile device
   • You may have to grant permissions to install unknown apps
   • For a more in-depth explanation, see this blog post from Android Authority
3. Sign-in with your Vanderbilt Microsoft account

To run unit tests and grade static code:

We have included a zip file of the latest code on GitHub. The zip file is not the entire local repository as that is too large a zip file to submit (Gradescope limits file sizes to 2GB). We strongly recommend that you git clone our repo from GitHub rather than try to work with this zip file.

The current Vanderbilt student solution to sharing Ubers or Lyfts is an unwieldy group chat on GroupMe. During school breaks, it requires users to scroll through a random assortment of messages, trying to determine if someone is leaving at the same time as them. This is both tedious, time-consuming, and prone to issues such as asking someone to carpool and being told that they already have a full group. This app will organize and sort all postings asking for carpool members and have a feature which will indicate if a carpool group is full already. The scope of the project will be a full Android app that works for Vanderbilt students looking for carpools to and from the airport or anywhere else. The scope will not extend to non-Vanderbilt students at this time, as it will require Vanderbilt credentials on sign in.

• Firebase project is named WeShare. Firestore is built within that Firebase project.
• Official Firebase docs - code examples React Native Projects are considered Web modular API projects.
• ReactNative + Expo specific docs - helpful for setup
• Expo Specific Docs - explain more about firebaseConfig.js

On the free plan, we are currently limited but should have enough free access for starting out.

We are currently in test mode (The default security rules for test mode allow anyone with your database reference to view, edit and delete all data in your database for the next 30 days)

• We are using Expo SecureStore to store authentication data.
• It will primarily just store the user id which will identify the user in the database.
• More info on handling sensitive data in ReactNative.
• Using Microsoft login to require Vanderbilt login following this document
• Using expo-auth-session instead of react-native-app-auth due to compatibility issues with Expo
• Redirect URI: com.wesharenative://oauth/auth/
• Expo Go always has a changing redirect uri which must be updated in Azure each time the project is run. This issue is specific to Expo Go and would not affect production as production would have a stable uri.
• Weshare login secret will be valid for 6 months (until 11 April 2026)

• Unit tests: Jest

  bun run test

Coverage report will be generated in the terminal when finished.

• Run bunx expo prebuild --platform android --clean
• Create local.properties file in android folder and add this line (assuming this is where your SDK is, can check in file explorer): sdk.dir=C:/Users/username/AppData/Local/Android/Sdk
• Run cd android
• Run ./gradlew clean
  • If get "Failed to delete some children. This might happen because a process has files open or has its working directory set in the target directory." just run the command again.
• In /weshare/android/app/build.gradle add manifestPlaceholders = [appAuthRedirectScheme: "weshare"] in the defaultConfige (right below buildConfigField...)
• Check /weshare/android/app/src/main/AndroidManifest.xml and replace android:scheme="weshare" with android:scheme="${appAuthRedirectScheme}" (there may be multiple occurences)
• Run ./gradlew assembleRelease
• APK can be found in /weshare/android/app/build/outputs/apk/release/
• Link to debugging conversation with chat https://chatgpt.com/share/691697f0-1d20-8012-97d8-f42bdbc33191

A guide on using Bun with Expo and EAS.

Bun is a JavaScript runtime and a drop-in alternative for Node.js. In Expo projects, Bun can be used to install npm packages and run Node.js scripts. The benefits of using Bun are faster package installation than npm, pnpm, or Yarn and at least 4x faster startup time compared to Node.js, which gives a huge boost to your local development experience.

Note: While Bun replaces Node.js for most use cases in your project, at this time, a Node.js LTS version is still required to be installed for the bun create expo and bun expo prebuild commands. These commands use npm pack to download project templates.

To create a new app using Bun, install Bun on your local machine.

1. Install dependencies

   bun install

2. Start the app (alt: see 3)

   bun run start

   From here, you can open the app in your mobile emulators using:

   • a for Android
   • i for iOS

   The full output lists the full options. Links to docs:

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

   You can start developing by editing the files inside the app directory. This project uses file-based routing.

   Make sure your emulators are launched BEFORE you try to run your app on them.

3. Run the app in a (launched) emulator

   # launch in ios
   bun run ios

   # launch in android
   bun run android

We use ESLint for linting and Prettier for formatting

# linting with ESLint
bunx expo lint

# formatting with prettier
bunx prettier --write .

To install any Expo library, you can use bun expo install:

bun expo install expo-av

EAS decides which package manager to use based on the lockfile in your codebase. If you want EAS to use Bun, run bun install in your codebase which will create a bun.lockb (the Bun lockfile). As long as this lockfile is in your codebase, Bun will be used as the package manager for your builds. Make sure to delete any lockfiles generated by other package managers.

Bun is installed by default when using EAS. See the Android server images and iOS server images to learn which version of Bun is used by your build's image.

To use an exact version of Bun with EAS, add the version number in eas.json under the build profile's configuration. For example, the configuration below specifies Bun version 1.0.0 for the development build profile:

{
  "build": {
    "development": {
      /* @info Use <CODE>bun</CODE> property in eas.json to specify the exact version.*/
      "bun": "1.0.0" /* @end */
      /* @end */
      /* @hide ... */
    } /* @end */
    /* @hide ... */
  }
}

You can start developing by editing the files inside the app directory. This project uses file-based routing.

Unlike other package managers, Bun does not automatically execute lifecycle scripts from installed libraries, as this is considered a security risk. However, if a package you are installing has a postinstall script that you want to run, you have to explicitly state that by including that library in your trustedDependencies array in your package.json.

For example, if you install packageA, which has a dependency on packageB and packageB has a postinstall script, you must add packageB in your trustedDependencies.

To add a trusted dependency in your package.json, add:

"trustedDependencies": ["your-dependency"]

Then, remove your lockfile and re-install the dependencies:

rm -rf node_modules', '$ rm bun.lockb', '$ bun install']}

If you're using sentry-expo or @sentry/react-native, these depend on @sentry/cli, which updates source maps to Sentry during your build. The @sentry/cli package has a postinstall script which needs to run for the "upload source maps" script to become available.

To fix this, add @sentry/cli to your trusted dependencies array in package.json:

"trustedDependencies": ["@sentry/cli"]

When you're ready, run:

bun run reset-project

This command will move the starter code to the app-example directory and create a blank app directory where you can start developing.

To learn more about developing your project with Expo, look at the following resources:

• Expo documentation: Learn fundamentals, or go into advanced topics with our guides.
• Learn Expo tutorial: Follow a step-by-step tutorial where you'll create a project that runs on Android, iOS, and the web.

Join our community of developers creating universal apps.

• Expo on GitHub: View our open source platform and contribute.
• Discord community: Chat with Expo users and ask questions.