Skip to main content

We have 2 amplitude accounts/orgs: 1 for events in production builds(from App store) and 1 to track and test events on test-builds.

After updating from production builds(from App store) to test-builds we find that test-builds(from test flight) still report events to the production org on Amplitude even though the API key is being updated to that of the different org.

Expected behaviour:
Events on test-builds are reported to a different org in amplitude once the API key is changed in the update.

Actual behaviour:
Events from both builds(test and production) are reported to the same org with 2 different device IDs depending on version of the app in use.

Note: the device ID is different for the events reported from the same device depending on the version of the app in use.

Has anyone else encountered this before, and have you found a fox to this?

Thanks for posting here @ksnag29. Were you able to get to the bottom of this? This guide on managing events is a good place to start - link, and I can help dive deeper if needed. Keep me posted!

Hi @ksnag29 ,

 

Thanks for writing in! I want to assist you on this. When you say you have two Amplitude accounts, do you mean separate Orgs or separate projects? What are the Org IDs and Project IDs? Can you also specify the Project ID(s) of importance for each? 

 

For test and production , which Org ID and which Project IDs are they respectively? I can then investigate. Have you compared the code for each version of your app? Have you ensured that it is the correct API and each user has updated to this where necessary? Thank you!

 

I look forward to your reply!

 

Kind Regards,
Denis

Thanks for writing in Denis,

To answer your questions:
We have 2 separate orgs - we use on for test-builds and one for prod builds.

Org ID(test) - analytics.amplitude.com/wardrobepoc
Project ID - 415344

Org ID(prod) - analytics.amplitude.com/looks-wardrobe
Project ID - 426893

Yes we have double checked the API keys and code for the version of our app, but still could not find the reason for this.

Looking forward to your reply, hope we can figure this out!

@ksnag29 ,

 

Thank you for your response! My apologies for the delay, I was OOO for a day. Can you PM me your email address you use for Amplitude? I would like to make a ticket so I can investigate this more thoroughly. Thank you!

 

Kind Regards,
Denis

Thanks for jumping in @Denis Holmes. I can also turn this into a ticket if that helps!

Hi @ksnag29. Closing the loop here. A few follow up questions:

  1. You were sending events to Org test without issues. You then started sending events to the Org Prod and here is the issue. The events you are sending to Prod are ending up in the Org Test? Is that correct? 
  2. How are you sending in the data? 
  3. Is it only these two projects (one in each org) that is affected?
  4. Can you show me a specific user you see this occurring for? 
  5. Which version(s) of the SDK(s) do you use?

Reply


Terms & ConditionsCookie settings