java.lang.NullPointerException: You need to initialize SDK first. EstimoteSDK.initialize(applicationContext, appId, appToken)

GitHub | kamilwlf | 4 months ago
  1. 0

    NullPointerException - Nearable packet parsing error

    GitHub | 4 months ago | kamilwlf
    java.lang.NullPointerException: You need to initialize SDK first. EstimoteSDK.initialize(applicationContext, appId, appToken)
  2. 0

    Google API Key logcat spam

    GitHub | 7 months ago | shmuelr
    java.lang.NullPointerException: You need to initialize Google API Key first. EstimoteSDK.setGoogleApiKey(key)
  3. 0

    NullPointerException happened in com.google.android.gms.DynamiteModulesA:686

    Google Groups | 6 months ago | Keven Wood
    java.lang.NullPointerException: Attempt to invoke > interface method 'android.view.View xq.e()' on a null object reference > at rx.a(:com.google.android.gms.DynamiteModulesA:686) > at rr.a(:com.google.android.gms.DynamiteModulesA:3308) > at rt.a(:com.google.android.gms.DynamiteModulesA:1230) > at avl.a(:com.google.android.gms.DynamiteModulesA:840) > at awb.run(:com.google.android.gms.DynamiteModulesA:45) > at android.os.Handler.handleCallback(Handler.java:739) > at android.os.Handler.dispatchMessage(Handler.java:95) > at android.os.Looper.loop(Looper.java:145) > at android.app.ActivityThread.main(ActivityThread.java:5832) > at java.lang.reflect.Method.invoke(Method.java) > at java.lang.reflect.Method.invoke(Method.java:372) > at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1399) > at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1194) > > We are using com.google.android.gms:play-services-ads:8.3.0. It was a > sudden dramatic increase crashes starting around June 13 > > > On Tuesday, June 14, 2016 at 11:45:23 AM UTC-4, Vu Chau (Mobile Ads SDK > Team) wrote: > >> Hi Keven, >> >> Thanks for confirming! >> >> Vu Chau >> Mobile Ads SDK Team >> >> On Monday, June 13, 2016 at 11:10:34 PM UTC-4, Keven Wood wrote: >>> >>> Hi Vu: >>> >>> >>> We have updated the version of Firebase from 9.0.0 to 9.0.2, also can >>> reproduce this issue. >>> >>> >>> Thanks. >>> >>> >>> BR >>> >>> Keven >>> >>> On Tuesday, June 14, 2016 at 12:41:41 AM UTC+8, Vu Chau (Mobile Ads SDK >>> Team) wrote: >>>> >>>> Hi Keven, >>>> >>>> At this time I don't have information whether there is a connection >>>> between the ProGuard issue (where the SDK behaves like its "lite" version >>>> that does not have the Google Play services components, hence the keep option) >>>> and this Native Ad NPE. >>>> >>>> Since there are two newer releases out since 9.0.0 (namely, 9.0.1 and >>>> 9.0.2), would you be able to try recompiling your app against either of >>>> those and let us know if the NPE recurs? >>>> >>>> Thanks! >>>> >>>> Vu Chau >>>> Mobile Ads SDK Team >>>> >>>> On Monday, June 13, 2016 at 5:27:19 AM UTC-4, Keven Wood wrote: >>>>> >>>>> >>>>> Hi Vu: >>>>> >>>>> >>>>> We are trying to fix this issue, find a doc in release note: Doc Link >>>>> <https://firebase.google.com/docs/admob/release-notes#android> >>>>> >>>>> >>>>> >>>>> - For this release only, apps that use ProGuard to post-process >>>>> their application need to add the following keep option >>>>> <http://proguard.sourceforge.net/manual/usage.html#keepoptions> to >>>>> their ProGuard configuration file: >>>>> -keep public @com.google.android.gms.common.util.DynamiteApi class >>>>> * { *; } >>>>> >>>>> >>>>> We do not add the line into our ProGuard file in our release version. >>>>> >>>>> >>>>> Is the issue related to the ProGuard configuration? >>>>> >>>>> >>>>> Should we fix this issue, if added the line into our ProGuard file? >>>>> >>>>> >>>>> BR >>>>> >>>>> Keven >>>>> >>>>> On Friday, June 3, 2016 at 11:58:46 PM UTC+8, Vu Chau (Mobile Ads SDK >>>>> Team) wrote: >>>>>> >>>>>> Thanks, Keven! >>>>>> >>>>>> I have informed the rest of the team of these crash instances >>>>>> yesterday, so I'll update you once I hear back from them. >>>>>> >>>>>> Vu Chau >>>>>> Mobile Ads SDK Team >>>>>> >>>>>> On Friday, June 3, 2016 at 12:23:13 AM UTC-4, Keven Wood wrote: >>>>>>> >>>>>>> HI Vu: >>>>>>> >>>>>>> >>>>>>> Thank you for your reply. >>>>>>> >>>>>>> >>>>>>> I have added my comments below your questions. >>>>>>> >>>>>>> >>>>>>> BR >>>>>>> >>>>>>> Keven >>>>>>> >>>>>>> On Friday, June 3, 2016 at 1:01:34 AM UTC+8, Vu Chau (Mobile Ads SDK >>>>>>> Team) wrote: >>>>>>>> >>>>>>>> Hi Keven, >>>>>>>> >>>>>>>> Your code looks fine. Calling .destroy() in the >>>>>>>> Activity#onDestroy() is correct. Just to make sure we are on the same >>>>>>>> page, I have a couple of questions for you: >>>>>>>> >>>>>>>> 1. Are you able to replicate this crash locally when you use >>>>>>>> our sample Native Ad project >>>>>>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fgoogleads%2Fgoogleads-mobile-android-examples%2Ftree%2Fmaster%2Fadmob%2FNativeExample&sa=D&sntz=1&usg=AFQjCNH_o1PIoTi9spreKXH8b47jE7D9Aw>? >>>>>>>> Let us know if you are able to. If the crash doesn't happen, something >>>>>>>> might be up with a specific creative that is shown. >>>>>>>> >>>>>>>> RE: These are random crash, i cannot reproduce the issue on my >>>>>>> device, The crash logs were found on my analyse server and produce by end >>>>>>> users, so i think i cannot reproduce this issue based on the sample code. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> 1. Would you be interested in implementing Native Ad Express >>>>>>>> <https://firebase.google.com/docs/admob/android/native-express>? >>>>>>>> With Native Ad Express, we are offloading all creative-specific logic to >>>>>>>> the server, so there's minimal work you'd need to worry about in your >>>>>>>> client-side code. That reduces any edge cases for code-based crashes. >>>>>>>> >>>>>>>> RE: I implemented the native ad before, but i need redefine the >>>>>>> layout of native ad, so I change to com.google.firebase:firebase-ads:9.0.0 >>>>>>> instead of com.google.android.gms:play-services-ads:9.0.0, then the issue >>>>>>> comes. I am sorry, i cannot implement the Native Ad Express to avoid the >>>>>>> issue. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Vu Chau >>>>>>>> Mobile Ads SDK Team >>>>>>>> >>>>>>>> On Thursday, June 2, 2016 at 3:18:30 AM UTC-4, Keven Wood wrote: Hi: >>>>>>>>> I used the latest Admob native sdk in my application. >>>>>>>>> The Doc link is: https://firebase.google.com/docs/admob/android/native-advanced The native ad is more beautiful than before, but i found some NullPointerExceptions in my UMeng server: >>>>>>>>> There are two categories issues: >>>>>>>>> 1. Happens on the android platform: 4.0, 4.1, 4.2, 4.3, 4.4: >>>>>>>>> java.lang.NullPointerException at rx.a(:com.google.android.gms.DynamiteModulesA:686) at rr.a(:com.google.android.gms.DynamiteModulesA:3308) at rt.a(:com.google.android.gms.DynamiteModulesA:1230) at avl.a(:com.google.android.gms.DynamiteModulesA:840) at awb.run(:com.google.android.gms.DynamiteModulesA:45)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    NullPointerException happened in com.google.android.gms.DynamiteModulesA:686

    Google Groups | 6 months ago | Keven Wood
    java.lang.NullPointerException: Attempt to invoke >> interface method 'android.view.View xq.e()' on a null object reference >> at rx.a(:com.google.android.gms.DynamiteModulesA:686) >> at rr.a(:com.google.android.gms.DynamiteModulesA:3308) >> at rt.a(:com.google.android.gms.DynamiteModulesA:1230) >> at avl.a(:com.google.android.gms.DynamiteModulesA:840) >> at awb.run(:com.google.android.gms.DynamiteModulesA:45) >> at android.os.Handler.handleCallback(Handler.java:739) >> at android.os.Handler.dispatchMessage(Handler.java:95) >> at android.os.Looper.loop(Looper.java:145) >> at android.app.ActivityThread.main(ActivityThread.java:5832) >> at java.lang.reflect.Method.invoke(Method.java) >> at java.lang.reflect.Method.invoke(Method.java:372) >> at >> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1399) >> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1194) >> >> We are using com.google.android.gms:play-services-ads:8.3.0. It was a >> sudden dramatic increase crashes starting around June 13 >> >> >> On Tuesday, June 14, 2016 at 11:45:23 AM UTC-4, Vu Chau (Mobile Ads SDK >> Team) wrote: >> >>> Hi Keven, >>> >>> Thanks for confirming! >>> >>> Vu Chau >>> Mobile Ads SDK Team >>> >>> On Monday, June 13, 2016 at 11:10:34 PM UTC-4, Keven Wood wrote: >>>> >>>> Hi Vu: >>>> >>>> >>>> We have updated the version of Firebase from 9.0.0 to 9.0.2, also can >>>> reproduce this issue. >>>> >>>> >>>> Thanks. >>>> >>>> >>>> BR >>>> >>>> Keven >>>> >>>> On Tuesday, June 14, 2016 at 12:41:41 AM UTC+8, Vu Chau (Mobile Ads SDK >>>> Team) wrote: >>>>> >>>>> Hi Keven, >>>>> >>>>> At this time I don't have information whether there is a connection >>>>> between the ProGuard issue (where the SDK behaves like its "lite" version >>>>> that does not have the Google Play services components, hence the keep option) >>>>> and this Native Ad NPE. >>>>> >>>>> Since there are two newer releases out since 9.0.0 (namely, 9.0.1 and >>>>> 9.0.2), would you be able to try recompiling your app against either of >>>>> those and let us know if the NPE recurs? >>>>> >>>>> Thanks! >>>>> >>>>> Vu Chau >>>>> Mobile Ads SDK Team >>>>> >>>>> On Monday, June 13, 2016 at 5:27:19 AM UTC-4, Keven Wood wrote: >>>>>> >>>>>> >>>>>> Hi Vu: >>>>>> >>>>>> >>>>>> We are trying to fix this issue, find a doc in release note: Doc Link >>>>>> <https://firebase.google.com/docs/admob/release-notes#android> >>>>>> >>>>>> >>>>>> >>>>>> - For this release only, apps that use ProGuard to post-process >>>>>> their application need to add the following keep option >>>>>> <http://proguard.sourceforge.net/manual/usage.html#keepoptions> to >>>>>> their ProGuard configuration file: >>>>>> -keep public @com.google.android.gms.common.util.DynamiteApi >>>>>> class * { *; } >>>>>> >>>>>> >>>>>> We do not add the line into our ProGuard file in our release version. >>>>>> >>>>>> >>>>>> Is the issue related to the ProGuard configuration? >>>>>> >>>>>> >>>>>> Should we fix this issue, if added the line into our ProGuard file? >>>>>> >>>>>> >>>>>> BR >>>>>> >>>>>> Keven >>>>>> >>>>>> On Friday, June 3, 2016 at 11:58:46 PM UTC+8, Vu Chau (Mobile Ads SDK >>>>>> Team) wrote: >>>>>>> >>>>>>> Thanks, Keven! >>>>>>> >>>>>>> I have informed the rest of the team of these crash instances >>>>>>> yesterday, so I'll update you once I hear back from them. >>>>>>> >>>>>>> Vu Chau >>>>>>> Mobile Ads SDK Team >>>>>>> >>>>>>> On Friday, June 3, 2016 at 12:23:13 AM UTC-4, Keven Wood wrote: >>>>>>>> >>>>>>>> HI Vu: >>>>>>>> >>>>>>>> >>>>>>>> Thank you for your reply. >>>>>>>> >>>>>>>> >>>>>>>> I have added my comments below your questions. >>>>>>>> >>>>>>>> >>>>>>>> BR >>>>>>>> >>>>>>>> Keven >>>>>>>> >>>>>>>> On Friday, June 3, 2016 at 1:01:34 AM UTC+8, Vu Chau (Mobile Ads >>>>>>>> SDK Team) wrote: >>>>>>>>> >>>>>>>>> Hi Keven, >>>>>>>>> >>>>>>>>> Your code looks fine. Calling .destroy() in the >>>>>>>>> Activity#onDestroy() is correct. Just to make sure we are on the same >>>>>>>>> page, I have a couple of questions for you: >>>>>>>>> >>>>>>>>> 1. Are you able to replicate this crash locally when you use >>>>>>>>> our sample Native Ad project >>>>>>>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fgoogleads%2Fgoogleads-mobile-android-examples%2Ftree%2Fmaster%2Fadmob%2FNativeExample&sa=D&sntz=1&usg=AFQjCNH_o1PIoTi9spreKXH8b47jE7D9Aw>? >>>>>>>>> Let us know if you are able to. If the crash doesn't happen, something >>>>>>>>> might be up with a specific creative that is shown. >>>>>>>>> >>>>>>>>> RE: These are random crash, i cannot reproduce the issue on my >>>>>>>> device, The crash logs were found on my analyse server and produce by end >>>>>>>> users, so i think i cannot reproduce this issue based on the sample code. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> 1. Would you be interested in implementing Native Ad Express >>>>>>>>> <https://firebase.google.com/docs/admob/android/native-express>? >>>>>>>>> With Native Ad Express, we are offloading all creative-specific logic to >>>>>>>>> the server, so there's minimal work you'd need to worry about in your >>>>>>>>> client-side code. That reduces any edge cases for code-based crashes. >>>>>>>>> >>>>>>>>> RE: I implemented the native ad before, but i need redefine the >>>>>>>> layout of native ad, so I change to com.google.firebase:firebase-ads:9.0.0 >>>>>>>> instead of com.google.android.gms:play-services-ads:9.0.0, then the issue >>>>>>>> comes. I am sorry, i cannot implement the Native Ad Express to avoid the >>>>>>>> issue. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Vu Chau >>>>>>>>> Mobile Ads SDK Team >>>>>>>>> >>>>>>>>> On Thursday, June 2, 2016 at 3:18:30 AM UTC-4, Keven Wood wrote: Hi: >>>>>>>>>> I used the latest Admob native sdk in my application. >>>>>>>>>> The Doc link is: https://firebase.google.com/docs/admob/android/native-advanced The native ad is more beautiful than before, but i found some NullPointerExceptions in my UMeng server: >>>>>>>>>> There are two categories issues: >>>>>>>>>> 1. Happens on the android platform: 4.0, 4.1, 4.2, 4.3, 4.4: >>>>>>>>>> java.lang.NullPointerException at rx.a(:com.google.android.gms.DynamiteModulesA:686) at rr.a(:com.google.android.gms.DynamiteModulesA:3308) at rt.a(:com.google.android.gms.DynamiteModulesA:1230) at avl.a(:com.google.android.gms.DynamiteModulesA:840) at awb.run(:com.google.android.gms.DynamiteModulesA:45)
  6. 0

    NullPointerException while switching from easymock version 3.2 to 3.4

    Stack Overflow | 11 months ago | Chris311
    java.lang.NullPointerException: Have you forgotten to instantiate classUnderTest?

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.NullPointerException

      You need to initialize SDK first. EstimoteSDK.initialize(applicationContext, appId, appToken)

      at com.estimote.sdk.internal.Preconditions.checkNotNull()
    2. com.estimote.sdk
      BeaconService$3$1.run
      1. com.estimote.sdk.internal.Preconditions.checkNotNull(Preconditions.java:21)
      2. com.estimote.sdk.cloud.internal.InternalEstimoteCloud.getInstance(InternalEstimoteCloud.java:71)
      3. com.estimote.sdk.service.internal.NearableResolver$1.load(NearableResolver.java:28)
      4. com.estimote.sdk.service.internal.NearableResolver$1.load(NearableResolver.java:25)
      5. com.estimote.sdk.internal.utils.AsyncCache.get(AsyncCache.java:155)
      6. com.estimote.sdk.service.internal.NearableResolver.tryToResolve(NearableResolver.java:47)
      7. com.estimote.sdk.service.BeaconService$6.onLeScan(BeaconService.java:983)
      8. com.estimote.sdk.service.BeaconService$3$1.run(BeaconService.java:404)
      8 frames
    3. Android Platform
      HandlerThread.run
      1. android.os.Handler.handleCallback(Handler.java:739)
      2. android.os.Handler.dispatchMessage(Handler.java:95)
      3. android.os.Looper.loop(Looper.java:148)
      4. android.os.HandlerThread.run(HandlerThread.java:61)
      4 frames