Null pointer while getting item quantity

Question

question

wsadiq asked Jul 2, '19 Dan commented Jul 8, '19

Null pointer while getting item quantity

We have a native app on Clover. At one point in the app, we are trying to get quantity of line item and getting a null pointer exception.

List<LineItem> items = order.getLineItems();
for (LineItem item : items) {
     long qty = item.hasUnitQty() ? item.getUnitQty() : 1000;
}

In the above code, Order has been obtained using OrderConnector. The line that gets the item's quantity is generating a null pointer exception. Can anybody help explain what is wrong here?

Thanks in advance.

Orders LineItems

2

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

wsadiq commented · Jul 02, 2019 at 08:35 PM

I forgot to add, this is happening for only one of our merchants - not everybody. Furthermore, this started happening only about a week ago and our app has not been updated for over a month. So obviosuly this has something to do with the merchant's invenmtory but I cannot figure out what.

0 ·

wsadiq commented · Jul 05, 2019 at 08:06 PM

Hello. Can anybody help? This has become an urgent issue so any help from Clover's app developer support team will be greatly appreciated.

0 ·

Welcome to the
Clover Developer Community

Answer 1 · 2019-07-08T18:28:34Z

Dan answered Jul 8, '19 Dan commented Jul 8, '19

It looks like LineItem#isNotNullUnitQty() is what you want.

/** Checks whether the 'unitQty' field has been set, however the value could be null */
public boolean hasUnitQty() {
return genClient.cacheHasKey(CacheKey.unitQty);
}

/** Checks whether the 'unitQty' field is set and is not null */
public boolean isNotNullUnitQty() {
return genClient.cacheValueIsNotNull(CacheKey.unitQty);
}

2

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

wsadiq commented · Jul 08, 2019 at 08:12 PM

Ok. Thanks. Has anything changed. Our application has not been updated since February but some merchants just started getting this null pointer error in the last 2-3 weeks. SO I am a little puzzled as to what may have changed to suddenly cause this exception.

0 ·

Dan ♦ wsadiq commented · Jul 08, 2019 at 09:45 PM

No changes to the has/isNotNull behavior that I know of. I don't know if it started being explicitly set to null by a first or third party app. Given that it is only impacting one merchant, I'd guess that either a third party app, specific flow/item configuration etc why this is surfacing now.

0 ·

question