Again seems its a bug - in new kite3 api - java.lang.NullPointerException at java.lang.String.replace(String.java:2240) at com.zerodhatech.kiteconnect.KiteConnect.cancelOrder(KiteConnect.java:354)
java.lang.NullPointerException at java.lang.String.replace(String.java:2240) at com.zerodhatech.kiteconnect.KiteConnect.cancelOrder(KiteConnect.java:354)
@sujith , okies. Now wrt to the cancelOrder, my implemented factoryPattern was referring to the two Constants one zerodha another one was mine which was returning Constants.variety as null, that caused the above said exception from the kite api. It was bug from my side not kite bug. You can close this thread.
PS: in financial systems, we act very fast and there was no response from your side which provoked me to write into other thread. Dont take it personally Sijith, you are doing very well.
This forum is intended to be a community-driven wherein people help each other and not more like a support portal. We work on various projects which are developed in-house by Zerodha, sometimes there can be delayed responses.
FYI, In old API this was working -
My program fired a CO for HINDALCO, got orderID - 180220000275878
It generates a child order (triggerpending) with id 180220000275888
So -
Parent orderId[180220000275878],childOrderId[180220000275888]
Checking parent order status
---getOrderStatus() - 180220000275878 COMPLETE
Parent orderId[180220000275878] with status : COMPLETE
Parent status is COMPLETE, now status of child
---getOrderStatus() - 180220000275888 TRIGGER PENDING
Child orderId[180220000275888] with status : TRIGGER PENDING
Now Closing/Exiting Child orderId[180220000275888] with status[TRIGGER PENDING]
EXIT-ORDER to xchange of parentOrderId[180220000275878] for childOrderId[180220000275888]
I called -
kiteConnect.cancelOrder(String orderId, String parentOrderId, String variety) throws KiteException, IOException {...}
Giving exception -
java.lang.NullPointerException
at java.lang.String.replace(String.java:2240)
at com.zerodhatech.kiteconnect.KiteConnect.cancelOrder(KiteConnect.java:354)
It seems to be working fine at our end. You can enable debugging to check more details.
PS: Please stop spamming other threads.
Is there any sandbox testing avbl?
thanks.
We don't have a sandbox. We are waiting for APIs from our vendor TR.
Now wrt to the cancelOrder, my implemented factoryPattern was referring to the two Constants one zerodha another one was mine which was returning Constants.variety as null, that caused the above said exception from the kite api.
It was bug from my side not kite bug.
You can close this thread.
PS: in financial systems, we act very fast and there was no response from your side which provoked me to write into other thread. Dont take it personally Sijith, you are doing very well.