Open pixelmatrix opened 7 years ago
Thanks! I think the fix should be in the integration. Looks like Mixpanel needs to be initialized on the main thread, so the integration should queue calls to the main thread.
Surprised we haven't noticed this before though.
cc @ladanazita
No problem. We only noticed because Xcode 9 now throws warnings for this scenario.
@f2prateek @ladanazita Any update on when this might be fixed, and an updated version released?
Hi @jx2 and @pixelmatrix ,
Sorry for the delay here. I'm going to track this internally and add this to our list to fix — I can't give an ETA at the moment but will update as soon as I have more.
Thanks for your patience! Ladan
Thanks for the info - much appreciated!
Hi @ladanazita. Do you know when this might be resolved?
@jx2 Hey John, Sorry for the delay here. It is still in our backlog at the moment. We haven't had any further reports on this, so it hasn't been prioritized.
I will keep you updated as soon as I have more.
Thanks for your patience
Our app is reporting that Segment-Mixpanel is accessing UI code from the wrong thread in Xcode 9. Here's the stack trace it gives:
Seems the issue is that SEGIntegrationsManager updateIntegrationsWithSettings is using it's own queue, which eventually hits Mixpanel's initialization code, which accesses UIApplication.shared. delegate.
I'm honestly not sure which project the fix should belong to, but I wanted to raise the issue since we've been seeing it every time the app launches.