Publisher is not working during market hours and orders are not getting placed with no errors but orders are getting placed and getting rejected during non market hours as expected. Please advise. Coding was done for banknifty options spread with limit order.
The code seems fine. Can you elaborate what do you mean by not working? Does screen become empty or you don't get to see success page? Can you take a screenshot and paste it?
This is one example of an order getting submitted after market hours and getting rejected as expected. Same submission does not come to kite during market hours. Please advise.
@eeesathiaeee Tested your script after removing your symbol get logic and it works fine and order shows up in orderbook once I place it. Please be more specific about the issue like were you able to place the order but doesn't shows up or it doesn't even load the publisher page.
I am able to see the place order button during market hours but clicking the place order and finish buttons does not bring the order to kite. Should i add double quotes to the symbol. Even if that is the case it is working perfectly during non market hours. Please advise.
Make sure you are not passing numbers as a string like a price, trigger price, square off etc and send tradingsymbol, exchange, order type etc as strings.
Everything is being passed as suggested. Main question is how it works during non market hours correctly. Could you please advise what is the main validation/logic difference at kite side during and after market hours which will resolve the original issue.
I am attaching all the codes(both the web version and the apk) for you to verify the codes and reproduce the behaviour. This works perfectly during non market hours but not during market hours. Please let me know your findings.
Please input banknifty call strike price and put strike price(both for buys) and a common limit price and a common lot size in multiples of 40. Click the 'Check' button first and then the 'Trade' button. This can be done in any version(web html version or android version).
@eeesathiaeee The code example you have given is for a Cordova application. But you are using Publisher JS plugin in it which is meant to be used in a browser environment. For a mobile application Basket order is more appropriate. You have to make a POST request as described in the link to a new WebView window in your app.
As you requested we tested in browser and in the app during market hours. In the browser, it successfully placed the orders. In the app, after clicking trade it was showing Kite login screen in a very small space just below the table. This is probably because of JS plugin. Try the Basket order(Publisher - Offsite orders).
Also, next time onwards try to give more details such as the platform you are working on, the flow of the process, errors if any, versions affected, screenshots etc. which will help us to easily diagnose the issue.
Thanks for all your support. I just embedded all the codes into a single html and trading with the mobile browser since the app version for the same codes does not work during market hours. Again, great support provided, thanks!!!
Does screen become empty or you don't get to see success page? Can you take a screenshot and paste it?
This is one example of an order getting submitted after market hours and getting rejected as expected. Same submission does not come to kite during market hours. Please advise.
Please input banknifty call strike price and put strike price(both for buys) and a common limit price and a common lot size in multiples of 40. Click the 'Check' button first and then the 'Trade' button. This can be done in any version(web html version or android version).
As you requested we tested in browser and in the app during market hours. In the browser, it successfully placed the orders. In the app, after clicking trade it was showing Kite login screen in a very small space just below the table. This is probably because of JS plugin. Try the Basket order(Publisher - Offsite orders).
Also, next time onwards try to give more details such as the platform you are working on, the flow of the process, errors if any, versions affected, screenshots etc. which will help us to easily diagnose the issue.
Thank you.