I am unable to login kite button using Chrome in any android version but working with MI, JIo etc. The login process is simply getting failed. I have Tried with multiple versions and the result was the same. Pls check Zerodha's own example in your mobile with the latest updated chrome browser. https://kite.trade/publisher-demo. Correct me if I am wrong.
If so feel some issues at my end. Both PIN and 2FA levels getting failed with a message like " Please complete login before verification" but working fine with other browsers in android...
Cookies are fine...it has some basic issues since I am able to log with kite web ... login session expires while completing 2FA or PIN, and all the three mobiles that the error rectified belong to Xiaomi.
Sorry my bad, I thought this is fixed. This seems to be happening because of chrome's new cookie policy. We have informed the team to take a look at this. This involves a lot of changes at our end. So we would suggest using an alternate browser in the meanwhile.
Thanks Sujith. Understand it is difficult time. Just, if you can put some TAT or how much time it took last time to resolve, it would help us a lot. Just for info, we (Mahogha) are an early stage startup working on multi user application.
Hi @sujith any update on this issue, looks like it seems to be impacting multiple users.....could you please investigate this and fix it at the earliest.
@yogesh.karale @sujith I am using 90.0.4430.216 on iPhone 7 and the Kite Authentication fails. Just to clarify I am not referring to the direct login to Kite on the mobile browser. I am referring to the login via my website using Kite Publisher which redirects to Kite for login. I have checked many of my friends on both iPhone and Android with various other browsers including Opera and Firefox, in all of them the issue is the same, it does not go beyond the login part.
@sujith could you please guide us and let us know if using Kite publisher via a Mobile App (on Android and Apple) will resolve this issue ? Does Kite publisher work on a Mobile App without having to invoke a browser session on the mobile ?
@sujith so the question is does WebView help in this case ? instead of using the usual browser ? Could you please let me know how long it could take to resolve this issue or what are the alternatives to execute via Mobile ?
@sujith I am using the latest version of Chrome browser on iPhone 7 and there is no option to enable / disable cookies. So could you please let me know where you can see to do this ?
@sujith I believe it is the same iFrame cookie management issue that is also causing the login to fail in iPhones as well. So what is the status of this issue and could you please let us know how much more time your team may require to fix this ? I believe the issue was reported nearly 9 months back and has been unresolved since then.
@vatsarj, Like I have mentioned earlier, there was an issue nine months back and we had added a fix. It seems to have broken after the latest update. Our team is looking into this.
Regarding enabling cookies on chrome, you can go to browser settings > privacy > clear browsing data > Cookies, Site Data must be turned on.
@vatsarj i got it just tagged you to request update from @sujith on the issues raised by you (snapshots provided by u). As we were facing the same issue as well.
Hi, There is some issue in Zerodha publisher API button since yesterday, i am frequently getting an "Error while fetching session. Please reload the page message. "
Please suggest. This issue is happening at my end. When I checked zerodhas demo page, it is showing the same error there as well. Kindly suggest.
I am using chrome version 92.0 but this issue can be replicated even on other browsers. I cleared the cookie as well as did a hard refresh but the issue is persisting. We are currently 7-8 people who are using this, but we may also need to extend this to a few other folks. Kindly suggest, as we are blocked on execution.
@rubaljhavar, Others are also facing the same issue? I just tried on chrome latest version and it seems fine for me. Just trying to gather more information to debug this issue.
Hi @sujith and @rakeshr I wanted to share a Youtube video I have created on how by making a small settings change for iPhone users one can overcome the issue being faced. Please watch and share
Can you check your browser version?
Click here to watch The screen Record
We have informed the team to take a look at this. This involves a lot of changes at our end. So we would suggest using an alternate browser in the meanwhile.
We had done some changes to fix this. It seems like with the new chrome update it is broken again. Our team is looking into this.
Just for info, we (Mahogha) are an early stage startup working on multi user application.
Thanks again for prompt response.
We have informed the concerned team to take a look at this. They are working on this.
Can you please share which G chrome version are you using? I am having no problem. Currently, I am using 90.0.4430.212.
I have checked many of my friends on both iPhone and Android with various other browsers including Opera and Firefox, in all of them the issue is the same, it does not go beyond the login part.
This is because of the change in the policy of iFrame cookie management, our team is looking into this issue.
Like I have mentioned earlier, there was an issue nine months back and we had added a fix. It seems to have broken after the latest update. Our team is looking into this.
Regarding enabling cookies on chrome, you can go to browser settings > privacy > clear browsing data > Cookies, Site Data must be turned on.
We are exploring alternatives.
You can try offsite order execution since it doesn't have iFrame.
Please suggest.
This issue is happening at my end. When I checked zerodhas demo page, it is showing the same error there as well. Kindly suggest.
What platform are you using and browser version? Does a hard refresh solve this or clearing cookies will help?
Others are also facing the same issue? I just tried on chrome latest version and it seems fine for me.
Just trying to gather more information to debug this issue.