Fix ImsCallProfile parceling and add protection for invalid parcelables.
Two things: 1. The writeToParcel and readFromParcel in the ImsCallProfile never worked; they were not parceling the Bundle properly. 2. Ensuring on writeToParcel that invalid Bundle contents are removed and not sent across a Binder interface. The existing Bundle.filterValues method accomplishes this by ensuring only primitive types and android.* namespace parcelables are included in the Bundle. We use this to ensure that when the ImsCallProfile instances cross the binder call boundary, package-local Parcelables don't cause the Bundle to be invalidated when unmarshaled in a place where the pacakge-local parcelable is not available. Test: Manual, also wrote new unit tests Bug: 65562929 Change-Id: Iea982d14a053414b9a4daba998c021c61902119d
Loading
Please register or sign in to comment