Skip to content

ChurchApps/B1Mobile

Repository files navigation

B1 Mobile

B1 Mobile is the mobile app companion to the B1.church app. It runs on both iOS and Android and provides the same features as the web version including online giving, self-check-in for attendance, live streaming of services, and an interactive member directory. Visit B1.church to learn more.

Preview

Get Involved

🤝 Help Support Us

The only reason this program is free is because of the generous support from users. If you want to support us to keep this free, please head over to ChurchApps or sponsor us on GitHub. Thank you so much!

🏘️ Join the Community

We have a great community for end-users on Facebook. It's a good way to ask questions, get tips and follow new updates. Come join us!

⚠️ Report an Issue

If you discover an issue or have a feature request, simply submit it to our issues log. Don't be shy, that's how the program gets better.

💬 Join us on Slack

If you would like to contribute in any way, head over to our Slack Channel and introduce yourself. We'd love to hear from you.

🏗️ Start Coding

If you'd like to set up the project locally, see our development guide. For this app:

  1. Copy dotenv.sample.txt to .env
  2. Run npm i to install dependencies

Release build

  1. Hardcode stage to prod EnvironmentHelper.ts
  2. Increment the version number in app.config.js, package.json, android/app/build.gradle and ios/B1Mobile/Info.plist
  3. Run npm run build:android to generate a Google Play release
  4. Run npm run build:ios to generate an iOS release

iOS Versioning and Submission

To avoid App Store rejections after the Expo eject, keep the native project in sync before each iOS release.

  1. Update expo.version and expo.ios.buildNumber in app.config.js (and bump package.json if needed).
  2. Mirror those values into the native project:
    • Set CFBundleShortVersionString and CFBundleVersion in ios/B1Mobile/Info.plist.
    • Update MARKETING_VERSION and CURRENT_PROJECT_VERSION in ios/B1Mobile.xcodeproj/project.pbxproj.
  3. Commit the changes so the release history is tracked.
  4. Run eas build --platform ios --profile production and wait for the build to finish.
  5. Submit with eas submit --platform ios --profile production (or use the Expo dashboard).
  6. If App Store Connect reports a duplicate version/build, repeat the steps with higher numbers and rebuild.

Sponsor this project

 

Contributors 13

Languages