Kotlin SurfaceView初始化报错求助：lateinit未初始化与空指针异常

问题重现 #

Kotlin代码 #

private lateinit var surface: SurfaceView
private var _binding: FragmentItem2Binding? = null
private val binding get() = _binding!!

override fun onCreateView(
    inflater: LayoutInflater, container: ViewGroup?,
    savedInstanceState: Bundle?
): View? {
    _binding = FragmentItem2Binding.inflate(inflater, container, false)
    return binding.root
}

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    surface?.findViewById<SurfaceView>(R.id.surf)
    this.surface!!.holder!!.addCallback(object : SurfaceHolder.Callback {
        override fun surfaceCreated(holder: SurfaceHolder) {
           TODO("Not yet implemented")
        }

        override fun surfaceChanged(
           holder: SurfaceHolder,
           format: Int,
           width: Int,
           height: Int,
        ) {
           TODO("Not yet implemented")
        }

        override fun surfaceDestroyed(holder: SurfaceHolder) {
           TODO("Not yet implemented")
        }
    })
}

XML布局代码 #

<SurfaceView
    android:layout_width="400sp"
    android:layout_height="400sp"
    android:id="@+id/surf"
/>

报错信息 #

• 使用lateinit声明时：

  kotlin.UninitializedPropertyAccessException: lateinit property surface has not been initialized
  

• 改为可空类型private var surface: SurfaceView? = null时：

  java.lang.NullPointerException
  

错误原因 #

1. 未正确初始化surface变量：代码里surface?.findViewById<SurfaceView>(R.id.surf)是错误写法——surface本身未赋值，调用它的findViewById没有意义，且这行代码也没有将找到的View赋值给surface。
2. 滥用!!操作符：直接用!!强制解包未初始化的变量必然触发空指针，这是Kotlin中需要避免的危险操作。
3. 忽略ViewBinding的作用：已经使用ViewBinding的情况下，无需手动调用findViewById，直接通过binding.surf就能拿到布局中的SurfaceView实例。

解决方法 #

方案一：直接使用binding获取SurfaceView（推荐） #

不需要单独声明surface变量，直接通过binding操作，代码更简洁安全：

private var _binding: FragmentItem2Binding? = null
private val binding get() = _binding!!

override fun onCreateView(
    inflater: LayoutInflater, container: ViewGroup?,
    savedInstanceState: Bundle?
): View? {
    _binding = FragmentItem2Binding.inflate(inflater, container, false)
    return binding.root
}

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    // 直接通过binding获取SurfaceView，无需额外变量
    binding.surf.holder.addCallback(object : SurfaceHolder.Callback {
        override fun surfaceCreated(holder: SurfaceHolder) {
            // 实现你的逻辑
        }

        override fun surfaceChanged(
            holder: SurfaceHolder,
            format: Int,
            width: Int,
            height: Int,
        ) {
            // 实现你的逻辑
        }

        override fun surfaceDestroyed(holder: SurfaceHolder) {
            // 实现你的逻辑
        }
    })
}

override fun onDestroyView() {
    super.onDestroyView()
    _binding = null // 销毁时清空binding，避免内存泄漏
}

方案二：声明并正确初始化surface变量 #

如果确实需要单独的surface变量，确保正确赋值：

private lateinit var surface: SurfaceView
private var _binding: FragmentItem2Binding? = null
private val binding get() = _binding!!

override fun onCreateView(
    inflater: LayoutInflater, container: ViewGroup?,
    savedInstanceState: Bundle?
): View? {
    _binding = FragmentItem2Binding.inflate(inflater, container, false)
    return binding.root
}

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    // 从binding中获取实例并赋值给surface
    surface = binding.surf
    surface.holder.addCallback(object : SurfaceHolder.Callback {
        override fun surfaceCreated(holder: SurfaceHolder) {
            // 实现你的逻辑
        }

        override fun surfaceChanged(
            holder: SurfaceHolder,
            format: Int,
            width: Int,
            height: Int,
        ) {
            // 实现你的逻辑
        }

        override fun surfaceDestroyed(holder: SurfaceHolder) {
            // 实现你的逻辑
        }
    })
}

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

关键注意点 #

• 确保lateinit变量在使用前完成初始化，否则会触发UninitializedPropertyAccessException。
• 优先使用ViewBinding提供的直接引用，替代findViewById，减少空指针风险。
• 避免不必要的!!操作符，不确定变量是否为空时，使用安全调用?.或者空合并操作符?:。
• 在Fragment的onDestroyView方法中清空_binding，避免内存泄漏。

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