Issue : java.lang.NullPointerException: Attempt to read from field 'java.lang.String android.accounts.Account.type

Solar2D Android
#1

Hi everyone  :slight_smile:

I am having this issue in Google Play console when a pre-launch test is done on my app. The app does not crash but this issue: 'java.lang.NullPointerException: Attempt to read from field ‘java.lang.String android.accounts.Account.type’ was found when tested on Samsung Galaxy S6. Other mobile devices did not issue any errors. Any info from anyone who had this problem?

Here is the reference given by google play console:

FATAL EXCEPTION: main
Process: com.google.android.videos, PID: 22119
java.lang.NullPointerException: Attempt to read from field ‘java.lang.String android.accounts.Account.type’ on a null object reference
    at android.os.Parcel.readException(Parcel.java:1552)
    at android.os.Parcel.readException(Parcel.java:1499)
    at com.android.vending.contentfilters.IContentFiltersService$Stub$Proxy.getContentFiltersAndIntent(SourceFile:139)
    at com.google.android.videos.contentfiltering.ContentFiltersManager.saveContentFiltersToPreference(SourceFile:438)
    at com.google.android.videos.contentfiltering.ContentFiltersManager.access$100(SourceFile:81)
    at com.google.android.videos.contentfiltering.ContentFiltersManager$1.onServiceConnected(SourceFile:423)
    at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1314)
    at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1331)
    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:6837)
    at java.lang.reflect.Method.invoke(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:372)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)

#2

I have exactly the same issue right now on the same device. Only difference is that my app was designed with LIBGDX.  Just started working on it. I will be back here to see if help comes or if I fix it somehow. Goodluck!

#3

I have the same problem…

#4

Are you using any Google Play services in your app? (IAP, GPGS, AdMob)?

Rob

#5

@Rob, Now I have removed plugin.google.play.services and shared.android.support.v4 per your suggestion from  Android Server build failed forum. I did not use google play game services, IAP, Admob. I have Appodeal integration though and appodeal serves Admob ads also.

 

#6

@Rob, Appodeal help told me to include plugin.google.play.services and shared.android.support.v4  for appodeal ads to work. I am a bit confused now since you told me not to include _plugin.google.play.services _for using build after 2016.3005.

If you could please tell me about the plugin.google.play.services for why not to use after 2016.3005 since I googled about this plugin but could not find anything that explains fully.
And as for the shared.android.support.v4 if I want backward compatibility this plugin isn’t required anymore?Corona will handle it automatically? - These questions are just to understand the workings of these plugins.

 
And the build using 2017.3023 was successful also when I have included back plugin.google.play.services and shared.android.support.v4 the plugins.

#7

There has never been a need to include shared.android.support.v4 (I will contact them about this as it’s wrong information). 

In build 2016.3005 the Android Dependency System was officially introduced for all of our plugins, which makes including plugin.google.play.services obsolete and it should be removed to avoid potential build issues. The Dependency System will take care of including all dependencies for you automatically.

If you use a Corona build prior to 2016.3005 you need to include plugin.google.play.services, but it’s not recommended to use older Corona builds. The main reasons being that they use a very old version of Googe Play Services (4.2.42) and might also conflict with other plugins you may use. The version of Google Play Services included by the Android Dependency System is 9.6.1, and will not conflict with any other of our plugins you may use.

#8

Hi

@Rob and @ ingemar_cl I have moved the appodeal and plugin issue in this thread since I feel like I am going to a different topic. 

#9

Thanks for creating a new topic as it is indeed a new issue not related to this thread.

I’ll have a look at the new issue and reply back on that topic thread.

#10

Check thiso ne to know more about…nullPointerException

Johnson

#11

@Johnson Thank you for posting that link.  :)  It was a nice short tutorial about what is NullPointerException is and read all of it to learn more about it.

I am still looking for the cause of this error only S6 devices but not in any other devices. 

#12

I have exactly the same issue right now on the same device. Only difference is that my app was designed with LIBGDX.  Just started working on it. I will be back here to see if help comes or if I fix it somehow. Goodluck!

#13

I have the same problem…

#14

Are you using any Google Play services in your app? (IAP, GPGS, AdMob)?

Rob

#15

@Rob, Now I have removed plugin.google.play.services and shared.android.support.v4 per your suggestion from  Android Server build failed forum. I did not use google play game services, IAP, Admob. I have Appodeal integration though and appodeal serves Admob ads also.

 

#16

@Rob, Appodeal help told me to include plugin.google.play.services and shared.android.support.v4  for appodeal ads to work. I am a bit confused now since you told me not to include _plugin.google.play.services _for using build after 2016.3005.

If you could please tell me about the plugin.google.play.services for why not to use after 2016.3005 since I googled about this plugin but could not find anything that explains fully.
And as for the shared.android.support.v4 if I want backward compatibility this plugin isn’t required anymore?Corona will handle it automatically? - These questions are just to understand the workings of these plugins.

 
And the build using 2017.3023 was successful also when I have included back plugin.google.play.services and shared.android.support.v4 the plugins.

#17

There has never been a need to include shared.android.support.v4 (I will contact them about this as it’s wrong information). 

In build 2016.3005 the Android Dependency System was officially introduced for all of our plugins, which makes including plugin.google.play.services obsolete and it should be removed to avoid potential build issues. The Dependency System will take care of including all dependencies for you automatically.

If you use a Corona build prior to 2016.3005 you need to include plugin.google.play.services, but it’s not recommended to use older Corona builds. The main reasons being that they use a very old version of Googe Play Services (4.2.42) and might also conflict with other plugins you may use. The version of Google Play Services included by the Android Dependency System is 9.6.1, and will not conflict with any other of our plugins you may use.

#18

Hi

@Rob and @ ingemar_cl I have moved the appodeal and plugin issue in this thread since I feel like I am going to a different topic. 

#19

Thanks for creating a new topic as it is indeed a new issue not related to this thread.

I’ll have a look at the new issue and reply back on that topic thread.

#20

Check thiso ne to know more about…nullPointerException

Johnson