Android RecyclerView共享元素从FragmentB返回FragmentA过渡失效问题

核心问题分析 #

从FragmentB返回FragmentA时共享元素过渡失效，本质是返回阶段RecyclerView的目标条目未完成布局绑定，导致系统无法匹配到对应transitionName的View，或过渡触发时机不匹配。

解决方案1：为返回流程添加过渡延迟 #

你已实现进入时的延迟过渡，但返回时同样需要等待RecyclerView重新完成条目绑定与布局。修改FragmentA的代码，在视图状态恢复阶段处理返回过渡的延迟：

class FragmentA : Fragment() {
    private var _binding: FragmentABinding? = null
    private val binding get() = _binding!!
    private lateinit var adapter: Adapter

    override fun onCreateView(
        inflater: LayoutInflater, container: ViewGroup?,
        savedInstanceState: Bundle?
    ): View {
        _binding = FragmentABinding.inflate(inflater, container, false)
        // 初始化RecyclerView与适配器
        adapter = Adapter(requireContext(), mutableListOf())
        binding.recyclerView.adapter = adapter
        return binding.root
    }

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)
        // 进入Fragment时延迟过渡，等待数据加载与布局完成
        postponeEnterTransition()
        viewModel.data.observe(viewLifecycleOwner) { entries ->
            adapter.setData(entries)
            binding.recyclerView.doOnPreDraw {
                startPostponedEnterTransition()
            }
        }
    }

    override fun onViewStateRestored(savedInstanceState: Bundle?) {
        super.onViewStateRestored(savedInstanceState)
        // 返回Fragment时延迟过渡，确保RecyclerView条目已重新布局
        postponeEnterTransition()
        binding.recyclerView.viewTreeObserver.addOnPreDrawListener(object : ViewTreeObserver.OnPreDrawListener {
            override fun onPreDraw(): Boolean {
                binding.recyclerView.viewTreeObserver.removeOnPreDrawListener(this)
                startPostponedEnterTransition()
                return true
            }
        })
    }

    override fun onDestroyView() {
        super.onDestroyView()
        _binding = null
    }
}

解决方案2：使用稳定的transitionName替代位置 #

依赖位置作为transitionName存在风险——即使数据未修改，RecyclerView的复用机制也可能导致返回时位置对应的View未完成绑定。改用条目的唯一ID作为标识，确保匹配可靠性：

修改Adapter的onBindViewHolder：

override fun onBindViewHolder(holder: ViewHolder, position: Int) {
    val entry = entries[position]
    // 用条目的唯一ID生成transitionName
    holder.itemView.transitionName = "entry_${entry.id}"

    holder.button.setOnClickListener {
        val fragmentManager = (context as AppCompatActivity).supportFragmentManager
        val editFragment = FragmentB()

        val bundle = Bundle()
        bundle.putInt("entryId", entry.id)
        bundle.putInt("entryPosition", position)
        editFragment.arguments = bundle

        fragmentManager.beginTransaction()
            .addSharedElement(holder.itemView, holder.itemView.transitionName)
            .addToBackStack(null)
            .replace(R.id.fragmentContainerView, editFragment)
            .commit()
    }
}

修改FragmentB的transitionName设置：

override fun onCreateView(
    inflater: LayoutInflater, container: ViewGroup?,
    savedInstanceState: Bundle?
): View {
    _binding = FragmentBBinding.inflate(inflater, container, false)
    val entryId = arguments?.getInt("entryId") ?: -1
    // 与Adapter中一致的唯一ID标识
    binding.entry.root.transitionName = "entry_$entryId"
    
    binding.saveButton.setOnClickListener {
        requireActivity().supportFragmentManager.popBackStack()
    }
    
    return binding.root
}

解决方案3：为FragmentA配置返回过渡动画 #

确保FragmentA也配置了与FragmentB一致的共享元素返回过渡，避免过渡逻辑不匹配：

class FragmentA : Fragment() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        sharedElementReturnTransition = MaterialContainerTransform().apply {
            duration = 500
            scrimColor = Color.TRANSPARENT
        }
    }
}

额外优化点 #

• 返回时主动滚动到目标条目位置，确保View已被加载：

  override fun onViewStateRestored(savedInstanceState: Bundle?) {
      super.onViewStateRestored(savedInstanceState)
      val targetPosition = arguments?.getInt("entryPosition") ?: -1
      if (targetPosition != -1) {
          binding.recyclerView.scrollToPosition(targetPosition)
      }
      // 延迟过渡逻辑...
  }
  

• 检查FragmentB的sharedElementReturnTransition配置，避免与进入过渡的参数冲突。

内容的提问来源于stack exchange，提问作者TomPeterson