Is it possible to have two different mobile library manager extensions in the same profile. We need to use one for an earlier version (with 3.1 SDK) of the app and one for the new version(with 3.2 SDK).

syed_ubaise
Not applicable
syed_ubaise
When we were using iOS SDK 3.1, we had conditions in mobile library manager extension to filter out auto tracking of the object_class that were crashing the app. Now with the new 3.2 SDK we are doing only custom tracking and hence using 'autoTracked' is not equal to 'true' condition to do that. The problem is that we are not able to use both the conditions in combination in the extension. Is it possible to have two different exlusive mobile extensions to address this issue
2 REPLIES 2

Is it possible to have two different mobile library manager extensions in the same profile. We need to use one for an earlier version (with 3.1 SDK) of the app and one for the new version(with 3.2 SDK).

roshan_gonsalko
Employee Emeritus
roshan_gonsalko
Hi Syed, I faced a similar challenge when I was working with a client. We needed to ensure that the existing profile would work with the new version and old version of the app. We set the library manager to cater for both scenarios. For example: http://note.io/1nGIrDg Would this help you? Note: I thoroughly tested it on both the live app and the new version of the app before pushing the new profile version live but you should be able to do this in advance of your new version of the app being released so you don't need to worry about timing... Note2 : If you're struggling to get hold of an old build of the old version of the app which is pointing to 'dev' or 'qa' then you can always: 1. Proxy your mobile device via Charles: https://community.tealiumiq.com/posts/624994 2. Use Charles to change your app to point to the 'dev' or 'qa' version of your profile: http://bit.ly/charles_change_environment 3. Push your updated library extension to 'dev' or 'qa' and test on your proxy'd device This helped me a lot - hope it helps you too! Cheers, Roshan

Is it possible to have two different mobile library manager extensions in the same profile. We need to use one for an earlier version (with 3.1 SDK) of the app and one for the new version(with 3.2 SDK).

jason_koo
Employee Emeritus
jason_koo
Syed, We are currently working on multiple SDK version support but the current system will only publish the last Library Manager extension added. Recommended best practice at the moment is to create another profile in your account for your app using the v3.2 library.