cancel
Showing results for 
Search instead for 
Did you mean: 

Flutter SDK - Creating Anonymous Users with Device Info when SDK is Disabled

arella
Practitioner

Are there any companies who have used the Flutter SDK that would be willing to connect with our developer team? 

We are using the Flutter Braze SDK exclusively in our app for this integration and we just released to PROD. Currently we have the Braze SDK disabled using the disableSDK method in Flutter, but we noticed the users are sending the device information with anonymous IDs.

This is what our code block looks like:

final remoteConfigBraze = remoteConfigRepository.remoteConfigBraze;
      BrazePlugin? braze;
      if (remoteConfigBraze.enabled) {
        braze = BrazePlugin(
          customConfigs: {replayCallbacksConfigKey: true},
        )..enableSDK();
      }
Our assumption based on experience with other analytics packages was an explicit start, but it sounds like Braze is using an automatic start?  This is really confusing because we changed our code to only call the BrazePlugin IF we have our RemoteConfig is turned on, so we don't understand how this is still happening.  There is not any circumstance where the SDK is initialized by the user; with the code snippet provided, we are not even calling the BrazePlugin until after we've confirmed we have the configuration switched to enabled for the entire App. With this, our expected result is that absolutely no data should be passed to Braze when our configuration is disabled, yet somehow there are anonymous users being created with nothing but device data. 
 
If this were an issue of the SDK being called unintentionally by some section of our code, we would expect to see App data and Events being passed, but we have not seen that in any instance. 
 
Our issue with this finding is that we also are not able to reproduce in our testing environment. This never occurred in our extensive Development and only started happening once we moved to production. 
 
We have been in a back and forth with Braze support for over two weeks now and are at a standstill unable to identify the issue. We are wondering if any other companies encountered similar issues in their initial setup because this feels like an issue we should have been able to resolve.
0 REPLIES 0