subscriptionResult.getPurchasesList() may return null to cause NPE
See original GitHub issueThanks for the great project!
I used it in my App PureWriter and got a NullPointerException related to the BillingManager
(line: 316):
and
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
subscriptionResult.getPurchasesList() may return null ... - GitHub
getPurchasesList() may return null to cause NPE #92 ... After querying purchases, the flow will enter subscription result processing, ...
Read more >getPurchasesList Null Pointer Exception - java - Stack Overflow
returns an object where result.getPurchasesList() == null , which causes the NPE in line if(result.getPurchasesList().size() >= 0).
Read more >Java NullPointerException - Detect, Fix, and Best Practices
The root cause is NullPointerException in the statement user.getUserId().toLowerCase() because user.getUserId() is returning null.
Read more >Retrofitting null-safety onto Java at Meta
We developed a new static analysis tool called Nullsafe that is used at Meta to detect NullPointerException (NPE) errors in Java code.
Read more >Null Pointer Exception In Java - GeeksforGeeks
NullPointerException is thrown when program attempts to use an object reference that has the null value. These can be: Invoking a method from...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have similar the problem with the billing libray 1.2 purchasesResult.purchasesList always return null. I can’t check if a user paid to restore paid state. I need to make a new purchase and check if reponseCode return ITEM_ALREADY_OWNED
Oh and for the
size
issue, this is definitely a sample error since without checking the response code for OK, the logging logsAt least for Kotlin, it should be
This bug will not surface if your proguard strips all logs in production