Uploaded image for project: 'Learner'
  1. LEARNER-7374

Android - Implement feature flag parity for Segment-Firebase implementation

    Details

    • Type: Task
    • Status: Merged
    • Priority: Unset
    • Resolution: Unresolved
    • Affects versions: None
    • Fix versions: Mobile Release 2.20
    • Components: None
    • Labels:
      None

      Description

      Currently, Android and iOS have a slight difference in how they utilize the Segment and Firebase configurations and enable/disable features based on it.

      Current working:

      1. Android checks if Segment is enabled and Firebase Analytics is also enabled then Segment's integration for Firebase is used
      2. Whereas iOS checks if Segment is enabled and Firebase is configured properly (i.e. all Firebase keys are present in config) then Segment's integration for Firebase is used

      Updated workflow:
      We can achieve parity on both OS by changing the Firebase config as follows:

      FIREBASE:
          ENABLED: false
          ANALYTICS_SOURCE: 'firebase | segment | none'
          CLOUD_MESSAGING_ENABLED: false
          API_KEY: 'DUMMY_VALUE_REPLACE_with_API_KEY'
          CLIENT_ID: 'DUMMY_VALUE_REPLACE_with_CLIENT_ID'
          GOOGLE_APP_ID: 'DUMMY_VALUE_REPLACE_with_GOOGLE_APP_ID'
          GCM_SENDER_ID: 'DUMMY_VALUE_REPLACE_with_GCM_SENDER_ID'

      Acceptance Criteria

      1. Both mobile platform teams should have consensus on this updated workflow
      2. Feature flag wiki should be updated
      3. Application codes will need to update as well

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                Mian Khalid
                Reporter:
                Mian Khalid
                Team:
                Learner: Axinite (Mobile)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: