-
Notifications
You must be signed in to change notification settings - Fork 21
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
Comments
Currently, 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]. |
Edit: We shifted our process to keep Github issues open for feature requests. |
Thanks. Followed up privately |
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 toCustomerIO.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
The text was updated successfully, but these errors were encountered: