When using loadAssetIntoView for a video, Flurry will add two views to the viewgroup passed into the method. However, due to an internal behavior, one of these views will overwrite its own layout params with a RelativeLayout.LayoutParams in onConfigurationChanged(). Because of this, if the viewgroup passed in is not a RelativeLayout, it will crash whenever configuration changes (e.g. rotation).
I suggest at the very least documenting this behavior within the loadAssetIntoView documentation, but I additionally suggest either enforce runtime checks telling integrating devs of this requirement or getting rid of this behavior altogether.
When using
loadAssetIntoViewfor a video, Flurry will add two views to the viewgroup passed into the method. However, due to an internal behavior, one of these views will overwrite its own layout params with aRelativeLayout.LayoutParamsinonConfigurationChanged(). Because of this, if the viewgroup passed in is not a RelativeLayout, it will crash whenever configuration changes (e.g. rotation).I suggest at the very least documenting this behavior within the
loadAssetIntoViewdocumentation, but I additionally suggest either enforce runtime checks telling integrating devs of this requirement or getting rid of this behavior altogether.