在启动时崩溃面料 [英] Fabric crash at startup

查看:154
本文介绍了在启动时崩溃面料的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的应用程序崩溃在该行内部的onCreate()函数

  Fabric.with(这一点,新Crashlytics());

该设备是三星SM-G313 HZ,运行4.4.2
我已经报告给他们的Twitter开发论坛,但我的职位是automarked为垃圾邮件。

任何人都知道一个解决办法?

这是的onCreate 功能:

 公共无效的onCreate(){
        super.onCreate();
        Fabric.with(这一点,新Crashlytics());
        图表= ObjectGraph.create(getModules());        ImageLoaderConfiguration imageLoaderConfiguration =
                ImageLoaderConfiguration。
                        createDefault(getApplicationContext());
        ImageLoader.getInstance()的init(imageLoaderConfiguration)。        MMX.init(这一点,R.raw.initfile);
        MMX.registerListener(新MessageEventListenerForLockScreen(本));
        意向意图=新意图(的getString(R.string.wake_up_key));
        MMX.registerWakeupBroadcast(意向);    }

我已经宣布AndroidManifest面料

 <元数据
            机器人:名字=io.fabric.ApiKey
            机器人:值=mykeyhere_a1cff923b11afaab1be7b005474d99b912b3/>

logcat的:

  10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:致命异常:主要
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:工艺:funride.android.com.rideshare,PID:16717
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:java.lang.VerifyError:COM / crashlytics /安卓/核心/ CrashlyticsCore
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在com.crashlytics.android.Crashlytics<&初始化GT;(Crashlytics.java:29)。
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在funride.android.com.rideshare.application.CloudBikeApp.onCreate(CloudBikeApp.java:33)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在android.app.ActivityThread.handleBindApplication(ActivityThread.java:4593)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在android.app.ActivityThread.access $ 1500(ActivityThread.java:151)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在android.app.ActivityThread $ H.handleMessage(ActivityThread.java:1402)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在android.os.Handler.dispatchMessage(Handler.java:110)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在android.os.Looper.loop(Looper.java:193)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在android.app.ActivityThread.main(ActivityThread.java:5344)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在java.lang.reflect.Method.invokeNative(本机方法)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在java.lang.reflect.Method.invoke(Method.java:515)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run(ZygoteInit.java:860)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在com.android.internal.os.ZygoteInit.main(ZygoteInit.java:676)
10-06 13:31:53.452 16717-16717 / funride.android.com.rideshare E / AndroidRuntime:在dalvik.system.NativeStart.main(本机方法)


解决方案

这可能是你使用的是改造2.0测试版?

微博目前使用的1.8改造,直到改造2.0的最终版本将不会更新

讨论时,它的固定可以在这里找到,希望能进行更新: https://开头twittercommunity.com/t/java-lang-verifyerror/53974

My app crashed at this line inside onCreate() function

 Fabric.with(this, new Crashlytics());

The device is SAMSUNG SM-G313 HZ, running 4.4.2 I've reported to their Twitter dev forum, but my post is automarked as spam.

Anybody knows a workaround?

This is the onCreate function:

public void onCreate() {
        super.onCreate();
        Fabric.with(this, new Crashlytics());
        graph = ObjectGraph.create(getModules());

        ImageLoaderConfiguration imageLoaderConfiguration =
                ImageLoaderConfiguration.
                        createDefault(getApplicationContext());
        ImageLoader.getInstance().init(imageLoaderConfiguration);

        MMX.init(this, R.raw.initfile);
        MMX.registerListener(new MessageEventListenerForLockScreen(this));


        Intent intent = new Intent(getString(R.string.wake_up_key));
        MMX.registerWakeupBroadcast(intent);

    }

I've already declared fabric in AndroidManifest

<meta-data
            android:name="io.fabric.ApiKey"
            android:value="mykeyhere_a1cff923b11afaab1be7b005474d99b912b3"/>

Logcat:

10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime: FATAL EXCEPTION: main
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime: Process: funride.android.com.rideshare, PID: 16717
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime: java.lang.VerifyError: com/crashlytics/android/core/CrashlyticsCore
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at com.crashlytics.android.Crashlytics.<init>(Crashlytics.java:29)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at funride.android.com.rideshare.application.CloudBikeApp.onCreate(CloudBikeApp.java:33)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4593)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at android.app.ActivityThread.access$1500(ActivityThread.java:151)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1402)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:110)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at android.os.Looper.loop(Looper.java:193)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:5344)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at java.lang.reflect.Method.invokeNative(Native Method)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at java.lang.reflect.Method.invoke(Method.java:515)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:676)
10-06 13:31:53.452 16717-16717/funride.android.com.rideshare E/AndroidRuntime:     at dalvik.system.NativeStart.main(Native Method)

解决方案

It may be that you are using the retrofit 2.0 beta?

Twitter currently uses retrofit 1.8 and won't update until the final release of retrofit 2.0

Discussion that will hopefully be updated when it's fixed can be found here: https://twittercommunity.com/t/java-lang-verifyerror/53974

这篇关于在启动时崩溃面料的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆