无法启动接收器com.parse.ParseBroadcastReceiver上Trigger.io Android应用 [英] Unable to start receiver com.parse.ParseBroadcastReceiver on Trigger.io Android app

查看:279
本文介绍了无法启动接收器com.parse.ParseBroadcastReceiver上Trigger.io Android应用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经建立了与trigger.io一个Android应用程序,使用解析推送通知。 应用程序部署到Google Play上和推送通知已工作的罚款。最近重新构建并部署到谷歌播放应用程序的新版本,与锻造平台版本1.4.29。

I've an Android app built with trigger.io, using Parse push notifications. App is deployed to google play and push notifications have been working fine. Recently re-built and deployed to google play a new version of the app, with Forge platform version 1.4.29.

从那时起,我已经收到以下崩溃报告通过谷歌播放:

Since then I have been receiving the following crash reports through Google Play:

java.lang.RuntimeException: Unable to start receiver com.parse.ParseBroadcastReceiver: android.content.ReceiverCallNotAllowedException: IntentReceiver components are not allowed to register to receive intents
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2236)
at android.app.ActivityThread.access$1500(ActivityThread.java:130)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1271)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4745)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.content.ReceiverCallNotAllowedException: IntentReceiver components are not allowed to register to receive intents
at android.app.ReceiverRestrictedContext.registerReceiver(ContextImpl.java:125)
at android.app.ReceiverRestrictedContext.registerReceiver(ContextImpl.java:119)
at com.parse.ParseCommandCache.<init>(ParseCommandCache.java:132)
at com.parse.Parse.getCommandCache(Parse.java:450)
at com.parse.ParseObject.saveEventually(ParseObject.java:1022)
at com.parse.ParseInstallation.saveEventually(ParseInstallation.java:170)
at com.parse.ParsePushRouter.saveEventually(ParsePushRouter.java:92)
at com.parse.ParsePushRouter.ensureStateIsLoaded(ParsePushRouter.java:208)
at com.parse.ParsePushRouter.hasRoutes(ParsePushRouter.java:122)
at com.parse.PushService.startServiceIfRequired(PushService.java:129)
at com.parse.ParseBroadcastReceiver.onReceive(ParseBroadcastReceiver.java:19)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2229)
... 10 more

我已经彻底以下的Andr​​oid手机测试的应用程序,并没有能够复制错误我自己。

I have tested the app thoroughly on the following Android handsets and not been able to replicate the bug myself.

  • 三星GALAXY Nexus
  • 在三星Galaxy S2
  • 在三星Galaxy S

有人建议是怎么回事错在这里,我怎么能与Trigger.io解决?

Can someone suggest what is going wrong here and how I can fix it with Trigger.io?

推荐答案

此问题已修复伪造v1.4.37,其中包括一个更新解析Android SDK中V1.2.3。

This issue was fixed in Forge v1.4.37, which included an update to the Parse Android SDK v1.2.3.

  • Trigger.io释放网易
  • <一个href="https://parse.com/questions/androidcontentreceivercallnotallowedexception-when-registering-for-push-notifications"相对=nofollow>在解析Q&放的Bug报告; A
  • Trigger.io release ntes
  • Bug report on Parse Q&A

这篇关于无法启动接收器com.parse.ParseBroadcastReceiver上Trigger.io Android应用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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