Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Robustness for GDPR compliance #272

Open
Minishlink opened this issue Oct 23, 2024 · 1 comment
Open

[Bug]: Robustness for GDPR compliance #272

Minishlink opened this issue Oct 23, 2024 · 1 comment
Labels

Comments

@Minishlink
Copy link

Which Platforms?

Both

Which React Native Version?

0.74

Which @braze/react-native-sdk SDK version?

13.1.0

Repro Rate

100%

Steps To Reproduce

Hello, this is a general issue

Expected Behavior

  1. Developer should be able to set SDK enabled to false by default so that when users first opens the app, the SDK is disabled instead of enabled (this is separate from SDK initialization/configuration)
  2. The SDK should resume sending events properly after SDK has been enabled after it was initially disabled. Today, no events are received on the dashboard until the app calls again changeUser+requestImmediateDataFlush
  3. enableSDK should be a promise that resolves when the SDK is completely enabled
  4. It would be nice that the developer could be able to know if Braze is actually enabled or not (Braze.getIsEnabled()?)

Actual Incorrect Behavior

Verbose Logs

No response

Additional Information

A bunch of ugly workarounds are possible:

  1. Really complex to accomplish although in theory feasible but you would have to somehow make the initialization later. Haven't looked into it more.
  2. Call changeUser and requestImmediateDataFlush again after enabling Braze and waiting some milliseconds since enableSDK is not a promise.
  3. The very robust setTimeout 🙃
  4. Handle that info on the developer's side, but this is obviously precarious

Thanks

@Minishlink Minishlink added the bug label Oct 23, 2024
@hokstuff
Copy link
Collaborator

hokstuff commented Feb 5, 2025

Hi @Minishlink,

Thanks for filing this request and apologies for the late reply.

This feature request sounds like it may be similar to (or possibly be addressed by) a feature that is on our roadmap around allowing the integrator to Delay their Initialization of Braze, e.g. until an end user accepts a user prompt. Regarding the status of this feature, we are still in progress in architecting a consistent interface across iOS and Android and then figuring out how this would look in our "wrapper" SDKs like React Native and Flutter. We have the core functionality available on the Braze Swift SDK, but the next steps are part of a longer-term initiative.

To help shed signal on this feature, please contact your CSM to file a product request to let our Product team know of the clients who are waiting on this feature.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants