The Natwest Bank Feeds appear to be down? it is logging in but not exporting, the “export to quickfile” button is also dead.
I have tried re-installing the plugin but to no avail.
Thanks
Rob
An update to the NW feed was published last week due to a change that they made to a button name (discussion here). If you have the latest version (1.29) it should work fine.
EDIT:
Just checked on our test account, seemed to work as expected.
Yes I am on version 1.29, I have just re-installed and cleared the cache, still no luck, it will log on but will stick on the last process i.e. export to quickfile, the quickfile button is also unresponsive.
thanks
Rob
Have you installed any extensions lately? Perhaps something is blocking the request?
The only other thing I can assume is that NW have slightly different UI for different accounts. This would make it very hard to deduce from our end.
Try hitting F12 in Chrome, when you click the export button does anything appear in the panel below, I’d expect to see a red cross with an error message you can expand. This would provide a clue as to why it’s not working.
Hi Glenn
No, I have not installed any other extension, the only other I have enabled is Google Docs, I have been on holiday for 2 weeks, the changes obviously took place whilst I was away.
I can manually download for now but would expect not to be the only one with this issue.
F12 results below
window.webkitStorageInfo’ is deprecated. Please use ‘navigator.webkitTemporaryStorage’ or ‘navigator.webkitPersistentStorage’ instead.
DEBUG:simpleDeploy init deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:simpleDeploy setup deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:digitalAdoption init deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:digitalAdoption start deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:Adding css //server.lon.liveperson.net/visitor/lpdc/lpdastyles.css deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:Adding js //server.lon.liveperson.net/visitor/lpdc/eventsDispatcher.min.js deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:Removing dynButton chat-natwest-secure-ebanking-changeaddress-english deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:Removing dynButton chat-natwest-digital-adoption deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
2
Handshake event from : eventsDispatcher.min.js:1
3
received message at: https://www.nwolb.com from: https://server.lon.liveperson.net eventsDispatcher.min.js:1
received message at: https://server.lon.liveperson.net from: https://www.nwolb.com eventsDispatcher.min.js:1
3
received message at: https://www.nwolb.com from: https://server.lon.liveperson.net eventsDispatcher.min.js:1
Vars SET common.js:266
Vars ERASED common.js:287
Uncaught TypeError: Cannot read property ‘match’ of undefined natwest.js:213
DEBUG:simpleDeploy init deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:simpleDeploy setup deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:digitalAdoption init deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:digitalAdoption start deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:Adding css //server.lon.liveperson.net/visitor/lpdc/lpdastyles.css deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:Adding js //server.lon.liveperson.net/visitor/lpdc/eventsDispatcher.min.js deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:Removing dynButton chat-natwest-secure-ebanking-changeaddress-english deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
DEBUG:Removing dynButton chat-natwest-digital-adoption deploy2.asp?site=48759847&d_id=natwest-secure-ebanking&default=simpleDeploy:132
7
Uncaught TypeError: Cannot read property ‘match’ of undefined natwest.js:213
Thanks
Rob
This is what I suspected may have been the issue. It seems by fixing the other reported problem it’s broken other accounts. So NW are using different code in different accounts… or maybe they’re gradually upgrading users?
Leave this with me, it’s likely going to be 24 hrs before a fix can be issued but it should work fine thereafter.
Thanks for your help Glenn
Rob
An update was published yesterday, if you’re updated to version 1.30 this should now work fine.
Appears to be working now
Many thanks Glenn, great service as always!
1 Like
This topic was automatically closed after 6 hours. New replies are no longer allowed.