Merge pull request #76 from k4m2a/fix/force-disable-onboarding

Force-disable onboarding regardless of persisted state

Author: achalagrawal

src/state/session/agent.ts

@@ -211,6 +211,19 @@ export async function createAgentAndCreateAccount(
         logger.info(`createAgentAndCreateAccount: failed to set initial feeds`)
         throw e
       }),
+      /*
+       * Auto-follow the brand account. This used to happen at the end of
+       * onboarding (StepFinished), which is now skipped entirely, so it
+       * happens here as part of account setup instead.
+       */
+      networkRetry(3, () => {
+        return agent.follow(getActiveBrand().appAccountDid)
+      }).catch(e => {
+        logger.info(
+          `createAgentAndCreateAccount: failed to follow brand account`,
+        )
+        throw e
+      }),
       // wait for AA data to load first, then check state
       aa.then(() => {
         const {flags} = unsafeGetAndComputeAgeAssurance({did: account.did})

src/state/shell/onboarding.tsx

@@ -114,9 +114,15 @@ export function isOnboardingActive() {
 }
 
 function compute(state: persisted.Schema['onboarding']): StateContext {
+  /*
+   * Onboarding is disabled entirely (issue #67) - users go straight into
+   * the app after signup. The persisted step is deliberately ignored so
+   * stale state written by older builds (or any stray 'start' dispatch)
+   * can never re-trigger the onboarding screens.
+   */
   return {
     ...state,
-    isActive: state.step !== 'Home',
-    isComplete: state.step === 'Home',
+    isActive: false,
+    isComplete: true,
   }
 }