Closed HaseebArshad1 closed 1 year ago
Hello, @HaseebArshad1! Make sure to update for your next releases, logging system there is much more advanced.
Talking with our developers considering 3006...
@HaseebArshad1, as I've been informed, this error can occur, when you call profile methods when other mutational methods run:
activate
identify
logout
The thing with these methods is that they can modify user's profile ID. If you call identify
and then call (i.e.) updateProfile
before identify
has responded, you risk sending second request to nowhere.
I can currently only recommend to retry such requests and be knowledgeable about this. You can manually mutex this if you really need to.
I need to discuss with our team, whether I should add mutex in my layer...
That should answer the genesis of your problem, but how it came to grow recently — I do not know. Maybe your recent release introduced something?
@divanc Got it, Thanks!
Description
A bug happened! Hi @divanc, This error started to happen recently for alot of users. do you know what could be the reason for this? I'm not able to reproduce it but I'm having verbose logs for a 3k+ users who faced this issue!
followed by this log i.e
Can you please check and let me know what could be the reason for this issue? Thanks!
Version
v2.3.5
What platforms are you seeing the problem on?
iOS, Android
System info