wrong instance is being used sometimes-- seems to be related to react-native/storage

[uooq]

Using version 5.5.0 of this SDK

We've set up two amplitude instances in our react-native app. They log wholly different types of events, use different user IDs, custom device IDs, etc.

We're seeing occasional cases where the events logged to one of the instances are going to the wrong project. Based on when these mistakes happen and looking at the app state surrounding these mistakes, it seems to have something to do with the app suspending and resuming.

Total stab in the dark, but is it possible that pending events that can't be tracked are getting persisted (e.g. saved to AsyncStorage) and that when the sdk retrieves them, they're getting assigned to an incorrect instance?

[uooq]

I can confirm that this issue is still happening in 5.6.0.

I can also confirm that you guys don't seem to bother reading your issue reports nor do you seem to be particularly willing to investigate bugs that are reported through your support tools after ignoring them on the issues.

What I wonder is if an energetic PAYING customer were to find and fix the bug, would you bother to look at a pull request to fix your issues?

[sputh]

@uooq do you have a code snippet of how you're calling identify and logging events?

Just to double check, are you calling amplitude.getInstance(instance) before you log events?

[sputh]

I've created a ticket on our end, we'll prioritize it and get back to you soon

[sputh]

@uooq I found the piece of code that's causing the issue. I'll have a PR out soon

[sputh]

@uooq pr to resolve this issue: #204

[uooq]

Thanks, that's great. I assume you no longer need a code sample? I sent one a while ago to your support team that they were meant to send to you, but if you still need it LMK.