本文介绍了拿不到报告中乱舞的Android Analytics（分析）的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我已经整合乱舞分析在我的应用程序，但无法获得乱舞仪表板中的报告，但是我把它整合一样提到乱舞自述PDF。我实现了所有codeS需要与API密钥，但不知道为什么我没有收到任何报告。请建议就同一任何解决方案。请看看在下面的记录：
I have integrated Flurry Analytics in my application but unable to get the report on Flurry Dashboard however I integrated it same as mentioned in Flurry ReadMe PDF. I implemented all codes required for that with API Key but doesn't know why I am not receive any report. Please suggest any solution regarding the same. Please look on to the Log below:
日志详细信息：
10-28 16:50:29.502: I/dalvikvm(21929): Could not find method com.google.android.gms.ads.identifier.AdvertisingIdClient$Info.getId, referenced from method com.flurry.sdk.dj.v
10-28 16:50:29.502: W/dalvikvm(21929): VFY: unable to resolve virtual method 9042: Lcom/google/android/gms/ads/identifier/AdvertisingIdClient$Info;.getId ()Ljava/lang/String;
10-28 16:50:29.502: D/dalvikvm(21929): VFY: replacing opcode 0x6e at 0x0042
10-28 16:50:29.512: I/dalvikvm(21929): Could not find method com.google.android.gms.ads.identifier.AdvertisingIdClient$Info.isLimitAdTrackingEnabled, referenced from method com.flurry.sdk.dj.o
10-28 16:50:29.512: W/dalvikvm(21929): VFY: unable to resolve virtual method 9043: Lcom/google/android/gms/ads/identifier/AdvertisingIdClient$Info;.isLimitAdTrackingEnabled ()Z
10-28 16:50:29.512: D/dalvikvm(21929): VFY: replacing opcode 0x6e at 0x0006
10-28 16:50:29.522: I/dalvikvm(21929): Could not find method com.google.android.gms.ads.identifier.AdvertisingIdClient.getAdvertisingIdInfo, referenced from method com.flurry.sdk.dw.c
10-28 16:50:29.522: W/dalvikvm(21929): VFY: unable to resolve static method 9044: Lcom/google/android/gms/ads/identifier/AdvertisingIdClient;.getAdvertisingIdInfo (Landroid/content/Context;)Lcom/google/android/gms/ads/identifier/AdvertisingIdClient$Info;
10-28 16:50:29.522: D/dalvikvm(21929): VFY: replacing opcode 0x71 at 0x000a
10-28 16:50:29.522: W/dalvikvm(21929): VFY: unable to resolve exception class 1320 (Lcom/google/android/gms/common/GooglePlayServicesRepairableException;)
10-28 16:50:29.522: W/dalvikvm(21929): VFY: unable to find exception handler at addr 0x43
10-28 16:50:29.522: W/dalvikvm(21929): VFY: rejected Lcom/flurry/sdk/dw;.c ()Lcom/google/android/gms/ads/identifier/AdvertisingIdClient$Info;
10-28 16:50:29.522: W/dalvikvm(21929): VFY: rejecting opcode 0x0d at 0x0043
10-28 16:50:29.522: W/dalvikvm(21929): VFY: rejected Lcom/flurry/sdk/dw;.c ()Lcom/google/android/gms/ads/identifier/AdvertisingIdClient$Info;
10-28 16:50:29.522: W/dalvikvm(21929): Verifier rejected class Lcom/flurry/sdk/dw;
10-28 16:50:29.532: W/System.err(21929): java.lang.VerifyError: com/flurry/sdk/dw
10-28 16:50:29.532: W/System.err(21929): at com.flurry.sdk.dj$1.a(SourceFile:247)
10-28 16:50:29.532: W/System.err(21929): at com.flurry.sdk.fc.run(SourceFile:49)
10-28 16:50:29.532: W/System.err(21929): at android.os.Handler.handleCallback(Handler.java:733)
10-28 16:50:29.532: W/System.err(21929): at android.os.Handler.dispatchMessage(Handler.java:95)
10-28 16:50:29.532: W/System.err(21929): at android.os.Looper.loop(Looper.java:136)
10-28 16:50:29.542: W/System.err(21929): at android.os.HandlerThread.run(HandlerThread.java:61)
10-28 16:50:29.562: W/FlurryAgent(21929): Start session with context: com.handygo.rockasap.screens.SplashActivity@43046458 count:0
10-28 16:50:30.792: W/System.err(21929): java.io.IOException: SERVICE_NOT_AVAILABLE
10-28 16:50:30.802: W/System.err(21929): at com.google.android.gms.gcm.GoogleCloudMessaging.register(Unknown Source)
10-28 16:50:30.802: W/System.err(21929): at com.handygo.rockasap.services.SendDeviceInfoTask.doInBackground(SendDeviceInfoTask.java:74)
10-28 16:50:30.812: W/System.err(21929): at com.handygo.rockasap.services.SendDeviceInfoTask.doInBackground(SendDeviceInfoTask.java:1)
10-28 16:50:30.812: W/System.err(21929): at android.os.AsyncTask$2.call(AsyncTask.java:288)
10-28 16:50:30.822: W/System.err(21929): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
10-28 16:50:30.822: W/System.err(21929): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
10-28 16:50:30.852: W/System.err(21929): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
10-28 16:50:30.852: W/System.err(21929): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
10-28 16:50:30.852: W/System.err(21929): at java.lang.Thread.run(Thread.java:841)
10-28 16:50:31.982: D/dalvikvm(21929): threadid=1: still suspended after undo (sc=1 dc=1)
10-28 16:50:31.982: D/dalvikvm(21929): GC_FOR_ALLOC freed 993K, 6% free 19368K/20392K, paused 12ms, total 12ms
10-28 16:50:32.942: W/FlurryAgent(21929): FlurryDataSender: report 72374d1e-cb0e-4196-bd5e-349416cb112a sent. HTTP response: 200
code在启动画面：
Code in Splash Screen:
@Override
protected void onStart() {
super.onStart();
FlurryAgent.onStartSession(this, "Y29JTBGCWHXWGKXN47YS");
FlurryAgent.setLogEnabled(true);
FlurryAgent.setLogEvents(true);
FlurryAgent.setLogLevel(Log.VERBOSE);
}
@Override
protected void onStop() {
super.onStop();
FlurryAgent.onEndSession(this);
}
在此先感谢。
Thanks in advance.
推荐答案
您乱舞集成的反射也不会立竿见影。您需要保持耐心。 24小时大约需要RO反映乱舞仪表盘的变化。请检查乱舞仪表板的明天，让我知道，如果你面对同样的问题。
The reflection of your flurry Integration won't be immediate. You need to keep patience. Approximately it takes 24hr ro reflect changes on Flurry Dashboard. Please check the Flurry Dashboard tomorrow and let me know if you face the same problem.
这篇关于拿不到报告中乱舞的Android Analytics（分析）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！