-
Notifications
You must be signed in to change notification settings - Fork 549
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
Reseting AWSConfiguration at runtime for PinpointManager #3659
Comments
PinpointManager is not a singleton. You should just be able to create multiple instances of |
But I am already creating another instance every time I get a new configuration using this code:
And it seems to keep just the first configuration I provide for the first client. Is there anything more I should do? |
You cannot reconfigure AWSMobileClient, so the below will continue to yield the same results.
You are using this constructor for the PinpointConfiguration. You would need to write your own extension of the AWSCredentialsProvider and provide another AWSConfiguration. |
Ahh I see! Thank you very much! We can close this question. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Is it posible to reset the
PinpointConfiguration
in runtime?Currently I am initializing the PintpointConfiguration as follows:
This works fine but I need to change the configuration in runtime (I will have users whose data is sent to a different instance of Pinpoint based on their region) and it is always keeping the first configuration I have passed to it. So if for example I have an US user logged in and configure it with the us region instance, then if the user logouts and another user, in this case from EU region for example, logs in, it is keeping the US region even if I call this code again to reconfigure it.
Is there a way to make the PinpointManager to reconfigure in runtime? Thanks in advance!
Which AWS Services are you utilizing?
Environment(please complete the following information):
Device Information (please complete the following information):
Not specific to a certain device
The text was updated successfully, but these errors were encountered: