When CastActivityManager launches a session using a CastMediaSource with multiple app IDs, it just arbitrarily uses the first one, which is most likely not correct in some cases.  See associated TODO in cast_activity_manager.cc.