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

Support multiple workspaces #830

Open
wtmoose opened this issue Oct 25, 2024 · 3 comments
Open

Support multiple workspaces #830

wtmoose opened this issue Oct 25, 2024 · 3 comments

Comments

@wtmoose
Copy link

wtmoose commented Oct 25, 2024

Is your feature request related to a problem? Please describe.
Our app allows users to connect to multiple networks that we operate. Each network has its own unique CIO workspace. Users are only actively connected to one network at a time, so we call CustomerIO.initialize() when they switch between networks. However, subsequent calls to CustomerIO.initialize() are ignored (an unexpected behavior that doesn't seem to be documented anywhere).

Describe the solution you'd like
We'd like to either have the option of having multiple CIO instances or have the ability to reconfigure by calling CustomerIO.initialize() any time we need to change configuration.

Describe alternatives you've considered
We see no other option than to fork the repo and implement the desired functionality ourselves.

Additional context

@scotttwittrockcio
Copy link
Collaborator

Currently, CustomerIO.initialize() is designed to be called only once per app session. Repeated calls to initialize are intentionally ignored, as the SDK architecture supports a single active instance for a single workspace.

Are you able to share a little more about your specific use case? Specifically are you able to share any more details about what a "network" is, and why each network requires a separate workspace even though they are using the same app. If you'd rather share privately you can send an email to [email protected].

@scotttwittrockcio scotttwittrockcio closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2024
@scotttwittrockcio
Copy link
Collaborator

scotttwittrockcio commented Oct 28, 2024

We close off feature requests on the public repo once we start tracking them internally. Please feel free to respond to this thread with more insights or requests.

Edit: We shifted our process to keep Github issues open for feature requests.

@wtmoose
Copy link
Author

wtmoose commented Oct 28, 2024

Thanks. Followed up privately

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

No branches or pull requests

2 participants