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.
Mike_MYOBI want to re-iterate that this issue IS NOT caused by 3rd party apps using unsupported browser versions (in many instances, developers may not even be aware of the low level browser implementations used many layers down in their chosen technogy stacks and libraries, or the technologies chosen many years ago by developers no longer on site). It HAS BEEN triggered by MYOB making a change to their AUTH process without any warning or notification.
I can confirm that the credentials page is now rendering correctly, but that the AUTH process no longer works for our application. This means that anyone requiring urgent access to MYOB data at this time will have no success; as others have already pointed out this has impacted the payments to and from potentially 100s of people.
Inconvenience does not come remotely close to describing the situation that MYOB has created. The time required to prepare and release software into financial instiutions for very good reasons is excessive. I know I'd be looking way beyond just changing the integration with MYOB, I'd be looking at moving the integration to NOT-MYOB. Flippant "you fix your software" responses to an issue caused by MYOB are inexcusable. I also note that others are aready raising the question of liability, Trish_Lee Kerry_Busby what are your thoughts on this?
Sorry for the delay in response to you Liam.
Totally agree with your statement. As a developer partner of MYOB for over 20 years, I have never experienced this situation. Previously any changes that would affect 3rd Party apps were communicated to the Developer Partners well in advance so that any required changes could be done. In fact, a beta version was provided in advance of release.
Also, I can confirm that the credentials page is now rendering correctly, but that the AUTH process no longer works for our application.
We were not aware of the low-level browser implementations used many layers down in our chosen Technolgy libraries and unfortunately it is not something that we can fix overnight. We are looking at a minimum of 3 weeks to change, test and deploy to our clients.
The 'not our problem' attitude in the update response is totally irresponsible and bordering on complete arrogance to a group of what are actually also MYOB clients. As clients we also pay quite a substantial fee to MYOB to be part of a program that helps to ensure the MYOB everyday clients remain with MYOB as they are using Add-Ons that not only extend the usability and functionality of the MYOB product, but also tie them to the MYOB product because of the investment in the addon products which may not be available for another accounting software.
I am hoping that come Monday morning, someone at MYOB sees some sense, realises that the impact of this change without notification, has not only affected the addon developers as a group but a massive number of AccountRight online subscription users who use the affected apps and roll back the change to the AUTH process for a period of time to allow developers to adjust the apps and allow the clients to continue to use the system.
Otherwise, we will be looking at informing our clients publicly exactly why their software is no longer compatible with ours.
As a company, we pride ourselves and have an extremely high reputation for our support for our customers, with this issue caused completely by MYOB making a change to their AUTH process without any warning or notification, I have received some of the most abusive phone calls in the entire 26 years of our Company history.
I also am appalled that as of Sunday 18th Aug 2024 at 5pm AEST, after submitting a support request as suggested more than 72 hours ago, that I have had no response.
I would not be in business if it took me that long to respond or even acknowledge a support request.
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.
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.
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.
What rubbish, how could this be marked as a solution.
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_MYOB, 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.
