We're updating the issue view to help you get more done. 
Learn more or See the old view

iOS - Implement feature flag parity for Segment-Firebase implementation

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:

1 2 3 4 5 6 7 8 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

 

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Status

Assignee

Saeed Bashir

Reporter

Mian Khalid

Labels

None

Reach

None

Impact

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Stakeholders

None

Story Points

1

Sprint

None

Fix versions

Priority

Unset