I received a notification about Bundle mismatch - what does it mean?
When you declare your Asset on your Ogury dashboard, you're declaring a specific bundle - and for this bundle, you receive a unique Ogury Asset Key (OGY-xxxxxxx). This is the asset key that you need to use during your SDK integration process.
If, at any point, you do an integration with this Asset Key in a different Asset (different bundle than the one you declared on your Ogury dashboard), we will detect it and notify you that the bundle from which we are receiving requests is not matching the bundle we expect. This is called Bundle mismatch notification.
What do I need to do when I receive Bundle mismatch notification?
You need to contact us at firstname.lastname@example.org, or contact your dedicated Ogury account manager, and inform them that you're acknowledging the problem. In case you're not sure where the issue is coming from , our team will be able to give you more details so that you can successfully locate the source of bundle mismatch.
You then need to fix your integration quickly and make sure to :
- Declare all your Assets in Ogury dashboard, one by one
- Make sure to use dedicated Asset Key for each of your Assets - bundles and Asset Keys must match with what is declared on Ogury dashboard!
- For all Assets where bundle mismatch was detected, you need to fix the SDK integration with the right Asset Key, and release the updated app version on the store
I received a notification that my integration issue was resolved
When you fix your integration, we start to detect less requests coming from the wrong bundle - as the updated app version (with updated SDK integration) is being adopted, we're seeing a descending trend in the number of requests from the wrong bundle.
After a few days of descending trend, we consider that you have fixed your integration problem, and we send you a notification that we consider the issue to be resolved.