应用作出签署APK后崩溃? [英] App crashes after making a signed APK?

查看:239
本文介绍了应用作出签署APK后崩溃?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个运行精绝当我使用调试密钥库构建它的应用程序。这是第一次,我做了一个APK签署关于谷歌Play商店中发布。我通过USB电缆传输的签署的apk我的电话,安装了应用程序,现在当我尝试运行它,它崩溃。当我尝试打开它,它崩溃的权利。

我已经通过Crashlytics启用崩溃报告,并没有任何报告任何新的崩溃。

当我从Eclipse构建并运行它,这一切都运行良好。

在哪里寻找这个问题?

时logcat中的应用程序崩溃:

 一月7日至16日:23:28.200:E / ActivityThread(28536):无法找到com.facebook.wakizashi.provider.MessagesForegroundProvider供应商信息
1月七日至16日:23:28.200:E / ActivityThread(28536):无法找到com.facebook.katana.provider.MessagesForegroundProvider供应商信息


解决方案

真正的问题是,ProGuard的找不到解析库某些注释。我不得不添加以下行来得到它的工作:

  -keepattributes *注释*

I have an app that runs absolutely fine when I build it using the debug keystore. For the first time, I made a signed APK for release on Google PlayStore. I transferred the signed apk to my phone via the USB cable, installed the app and now when I try to run it, it crashes. It crashes right when I try to open it.

I have crash reporting enabled via Crashlytics and that doesn't report any new crashes either.

When I build it from Eclipse and run it, it all runs fine.

Where do I look for the problem?

Logcat when the app crashes:

07-16 01:23:28.200: E/ActivityThread(28536): Failed to find provider info for com.facebook.wakizashi.provider.MessagesForegroundProvider
07-16 01:23:28.200: E/ActivityThread(28536): Failed to find provider info for com.facebook.katana.provider.MessagesForegroundProvider

解决方案

The real issue was that ProGuard could not find certain annotations for Parse library. I had to add the following line to get it to work:

-keepattributes *Annotation*

这篇关于应用作出签署APK后崩溃?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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