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 embedded web browser in the application. I can also see another client has reported exactly the same issue. As far as I am aware, this issue has only started today. It appears something has changed in the MYOB web pages that IE does not like.
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.
MikeG1, There must be a workaround for this issue. I have 200+ invoices to export to MYOB and need to pay over 60 Suppliers today by 4 p.m.
I Spent over two hours on the phone with the MYOB Support team to find a workaround, but they could not find a solution. I was told to raise this issue with the API, but I do not have the Developer ID or API key to do so.
Like another user on this Forum, I have been using MYOB software for over 15 years, but I have never felt this helpless. Still waiting for some positive update in next couple of hours.
Hi DilipB
I know how helpless you feel, I have all my clients who use our 3rd Party app connecting to their online file that cannot function.
I have in the 20 years of being a MYOB developer partner, never had a major change that would impact 3rd party apps, not be communicated in advance of what is a catastrophic impact to their own MYOB subscription paying end user Clients.
I will let you know if I receive any information
Trish
Hi DilipB , as a user of an external program, your first line of support is with the developer of the add-on. They should already be aware of MYOB's response on this issue, and can advise you what they can/will do about it.
The MYOB support line is generally not up with the technical aspects of integrating addon programs.
Mike, as one of the developers impacted by this, the problem we are facing is zero notification, ownership or support from MYOB who triggered the issue in the first place by seemingly making changes to their AUTH processes without notifying anyone. All we get now is "not our problem". If the MYOB support line is not up with the technical aspects of what is going on with their own product...well, there we are.
The issue I have is that my apps used the Microsoft WebBrowser control (IE) to handle the OAuth process. Microsoft has released a new control called the EdgeBrowser control, but this doesn't seem to work with the redirects that happens in OAuth, as it requires a predefined list of trusted domains/URLs. If a URL isn't on the Trusted Domains list, the URL opens in a new default browser window instead of the control.
Has anyone got any luck on work around ? or has there been any update on this issue ?
We must find solution by tomorrow. It is going to have massive financial impact to us.
Hoping for some update/ Workaround on this issue. Please share.
Hi MikeG1
I also would like to highlight the brilliant support from Steve_PP who was amazingly generous with providing source code that enable us to complete the changes for our app.
The developers on this forum, who have provided their knowledge to assist others is what a really good community is about.
Thanks
Trish
Hi Liam
what is the solution to this issue ?
MyOB support said ( over phone) it is not issue on their end. This issue appear from today which is after the MYOB software update last night.
I've just submitted a ticket this morning, are there any updates or ETA on when a fix will be available? Thanks
Hi Liam and Mike,
Have you had any response from MYOB, all my clients are unable to print barcodes or do other functions via our 3rd Party app. They can manuaally enter into AccountRight, however they cannot print out their barcodes. Its getting a bit drastic as there is no timeline being given to date or updates on support requests enabling us to respond to their questions.
Thanks
trish
Hi Trish_Lee LiamM DilipB & Matiu
I have an update from our internal team that was investigating this. Thanks for your patience.
This is related to the 3rd party app developers using an old version of IE that has not been supported since 2022.
The developers of these apps will need to upgrade to a supported browser in order for services to be restored.
I understand that this is disruptive for your businesses and your customers, but it will be up to the app developers to resolve this for you.
Kind regards, Mike
Hi Mike
I think this is unacceptable comments and does not help the 3rd party integrators solve a problem that has become significant over the last 2 days.
Our App is in use by over 80+ users who have not been able to send important information to their MYOB.
These businesses are medium to large businesses with large quantities of transactions.
Some of them are already asking the question on who is to blame and who is responsible. From some of the reports coming in, some of these larger clients potentialy will be looking for someone to go after for compensation.
May I suggest that someone with authority in the MYOB API development team finds a solution urgently and updates this forum but more importantly all the support tickets that you have on this matter.
Hi Kerry_Busby
Thank you for speaking out, I have had a support ticket in for 23 hours with absolutely no response on it, the only response has been from MikeG1
Mike initially stated it was an issue with the change to the AUTH endpoint and it was being looked into. Now Mike is saying it is all on the developers, who were not even notified that there was a change coming in regard to the AUTH endpoint. Our 3rd Party app uses are in absolute limbo, like you we have a large number of users and the level of communication with MYOB API Development team is deplorable.
Thanks
Trish
We are the Developers of the 3rd Party App impacted by this.
So what you are saying is that that MYOB have made a change that has impacted 3rd Party apps, that there was no communication re the change and all 3rd Party developers must change and redeploy their apps.
Is there any way that MYOB can roll back the change and give 3rd Party app developers a time frame to develop and deploy??????
Trish
100%. It's totally unacceptable for this sort of global change to get rolled through and then to have the washing of hands over it. If we have to spend time making code changes, maybe we'd be better off looking at other platforms.
Mike - to confirm, due to an acknowledged change in MYOB you are requesting all third parties rebuild, re-test, re-package, re-certify, and redeploy their applications across their entire user base? This means that MYOB will not be making any further updates in their systems to resolve this?
HI Liam, thats correct, MYOB is unable to keep supporting these browsers and it is up to the 3rd party developers to update to a supported browser.
This will not be all 3rd parties, only those who have not already upgraded from an unsupported browser.
Can you provide an optional rollback of yesterday’s update? This is going to cause a lot of short term pain.
Hey Matiu and LiamM
To clarify, MYOB hasn't made a change to invalidate the browser, the browsers have stopped being compatible with our software as Microsoft no longer supports them.
The announcement about these old browsers was made by Microsoft on June 15 2022
https://learn.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge
We wont be able to roll back the update as a result of this
This is a repeat of what you have already said, but prior to that you said there was a change in the AUTH endpoint which MYOB clearly could, and really should, rollback. I've been doing this job for nearly 30 years, I've never come across a company so flipantly break something and then take no action to resolve. Breathtaking.
