Change version number to 0.1

packages/mobile/README.md

@@ -114,6 +114,8 @@ Note: if you change the file structure in [mobile], hot reloading might not work
 
 ## Submitting to app stores
 
+Use the "Publish" workflow to publish to the app stores
+
 ### Google Play Store (Android)
 
 ### Apple App Store (iOS)
@@ -122,6 +124,8 @@ Much (but not all) of the app store information (such as the app's description)
 
 You can update app store metadata via `yarn npx eas-cli metadata:push`. Maybe you could do `yarn npx eas-cli metadata:pull` first and see if there's any changes that were manually made that should be saved in store.config.json first though.
 
+Note that every time you publish, the BUILD number needs to be increased. Note that the BUILD number is not the same as the VERSION number (the version number is what real users see in the app store)
+
 ## Other Topics
 
 ### iOS Internal Distribution

packages/mobile/app.config.js

@@ -8,7 +8,7 @@ const releaseChannel = process.env.RELEASE_CHANNEL?.toLowerCase();
 export default {
  name: getAppName(),
  slug: "bloom-reader-lite-mobile", // Used in Expo URLs or the project name in Expo Go, I think. I don't think it needs to vary based on release channel.
- version: "1.0.0",
+ version: "0.1.0",
  owner: "bloombooks",
  orientation: "portrait",
  icon: "./assets/BloomIcon.png",
@@ -22,6 +22,7 @@ export default {
  ios: {
  supportsTablet: true,
  bundleIdentifier: getPackageIdentifier(),
+ buildNumber: 1,
  },
  android: {
  package: getPackageIdentifier(),