Error Connecting Windows App to MYOB
As of today several users are reporting issues with connections from our windows application to MYOB. I believe it is related to the underlying use of Internet Explorer as a part of the e...
Forum Discussion
We are back up and running - we had been using the .NET Framework WebBrowser control, and the approach we took was replacing that component with WebView2, which is also a Microsoft component. Grabbed from NuGet and required relatively minimal code changes. You will have a new dependency on having the WebView2 runtime installed on client machines. It is not present on all machines by default.
Hi NathanCrane Thank you for this update. It helped us to find the solution. Really appreciate you sharing this information.
This is great to hear NathanCrane , thank you for sharing, hopefully this is helpful to others who are having this issue. Thanks!
NathanCranethanks for sharing. I've found an ActiveX Control here that is basically WebView2 inside an ActiveX wrapper. I'm currently trialling it now in an MS Access form. The authentication appears to work, however I then get a message "desktop's server IP address could not be found". MikeG1 , can you confirm if "http://desktop" is still valid as the redirect URI?
Phil_Jeffrey_KCMaybe you're looking at the wrong property? When using WebBrowser the "http://desktop" was in the DocumentText property, after converting to WebView it's in Source.AbsoluteUri.
Hi Folks
I am going around in circles - I have just been told by Tana that everything is fixed yet I am still not being issued correct initial tokens.
My apps are built around MS Access - and the quickest was I found if the MYOB server is issuing tokens correctly is to post the initial
https://secure.myob.com/oauth2/account/authorize?client_id=xxxxxxxxxxxxxx&redirect_uri=http://desktop&response_type=code&scope=CompanyFile to a browser - chrome and I will see a code in the return address. Once I know that is working I can then go back into my own app and refresh and away it goes.
Since the 1st crash - I was off the air for 3 days until I found that this gave me 20 minute access - and told MYOB tues their refresh token was wrong.
After the MYOB fix tues - nothing worked.
I am dead - nothing gets me anything except offline tokens.
Has MYOB done something that this approach no longer works - if they are back online - what has changed.
My keys were revoked - and access permitted again - there is nothing my end that has changed.
Anyone go any ideas - surely I don't have to get access using their sdk only. I would have clients screaming for blood.
Regards The Doc
Hi Phil,
It is, but from memory I had to change up the regex slightly from the original example code, so just check exactly what's coming back in the url and adjust accordingly.
Kind Regards,
Nathan
