繁体   English   中英

Android Studio 升级到 Studio 4.2 Canary 5 后数据绑定错误

[英]Android Studio Error on Data Binding after upgrading to Studio 4.2 Canary 5

我正在使用数据绑定来扩充片段的视图。 在我将 Android Studio 升级到 4.2 Canary 5 之前它工作正常。它还要求我将gradle版本升级到4.2.0-alpha05升级默认语言功能到Java 8 但是现在数据绑定部分正在抛出NullPointerException 我在这里需要一些帮助。 下面是错误的痕迹。

2020-07-22 01:11:13.437 18307-18307/com.deamat.mydeamat.debug E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.deamat.mydeamat.debug, PID: 18307
    java.lang.RuntimeException: Unable to start activity ComponentInfo{com.deamat.mydeamat.debug/com.deamat.mydeamat.MainActivity}: java.lang.IllegalStateException: FragmentSignupBinding.in…          false
            ) must not be null
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2927)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2988)
        at android.app.ActivityThread.-wrap14(ActivityThread.java)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1631)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:154)
        at android.app.ActivityThread.main(ActivityThread.java:6682)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)
     Caused by: java.lang.IllegalStateException: FragmentSignupBinding.in…          false
            ) must not be null
        at com.deamat.auth.SignupFragment.onCreateView(SignupFragment.kt:27)
        at androidx.fragment.app.Fragment.performCreateView(Fragment.java:2698)
        at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:320)
        at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1187)
        at androidx.fragment.app.FragmentManager.addAddedFragments(FragmentManager.java:2224)
        at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1997)
        at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1953)
        at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1849)
        at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:2629)
        at androidx.fragment.app.FragmentManager.dispatchActivityCreated(FragmentManager.java:2577)
        at androidx.fragment.app.Fragment.performActivityCreated(Fragment.java:2722)
        at androidx.fragment.app.FragmentStateManager.activityCreated(FragmentStateManager.java:346)
        at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1188)
        at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1356)
        at androidx.fragment.app.FragmentManager.moveFragmentToExpectedState(FragmentManager.java:1434)
        at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1497)
        at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:2625)
        at androidx.fragment.app.FragmentManager.dispatchActivityCreated(FragmentManager.java:2577)
        at androidx.fragment.app.FragmentController.dispatchActivityCreated(FragmentController.java:247)
        at androidx.fragment.app.FragmentActivity.onStart(FragmentActivity.java:541)
        at androidx.appcompat.app.AppCompatActivity.onStart(AppCompatActivity.java:201)
        at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1256)
        at android.app.Activity.performStart(Activity.java:6959)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2890)
            ... 9 more

这是数据绑定调用

override fun onCreateView(
        inflater: LayoutInflater, container: ViewGroup?,
        savedInstanceState: Bundle?
    ): View? {
       val binding = FragmentSignupBinding.inflate(
            inflater,
            container,
            false
        )

        ...
}

注意:我在我的应用程序中使用了多个模块,并且我在每个模块中启用了数据绑定。 但是 login_fragment 布局与 Fragment class 位于同一模块内。

自从更新到 AS 4.2 Canary 5 / Gradle 4.2.0-alpha05 后,我们的数据绑定也被破坏了。 我们甚至无法构建我们的应用程序。

在我们的例子中,它似乎与自定义 BindingAdapter 相关。 从布局文件中删除它们的使用,可以构建应用程序 - 尽管缺少相应的逻辑。 真的不是一个解决方案,所以我们现在不得不降级到 Canary 4。

像这样做:

class PracticeFragment:Fragment() {
    private lateinit var binding: FragmentPracticeBinding//declare your binding 

    companion object {
        fun newInstance() = PracticeFragment()
    }
    override fun onCreateView(
        inflater: LayoutInflater,
        container: ViewGroup?,
        savedInstanceState: Bundle?
    ): View? {
        binding = FragmentPracticeBinding.inflate(inflater,container,false)
        return binding.root
    }

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {

    }
}

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM