Our engineers recommend against doing so.
We don’t have proof that it definitely would cause problems or fail, but it can easily be haphazard and cause subtle behaviors that influence the behavior of the SDK, thereby not giving you an accurate picture of how to SDK and product works. It could also bring down your app altogether. You have now been warned.
Part of the reason behind this risk is that there are global error handling classes, and the framework has its own error handling classes as well, so if 2 SDK’s are both consuming from or watching what these classes are doing, it could create a race condition, or one sdk could block the other sdk, or both execute at once (same thread, or multiple threads) and cause problem, or cause some other unwanted behavior not described here. How these interactions work is not well understood, and that’s because it’s risky to attempt them in general and it’s not the intended or supported use case in general.