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
Hi everyone, thanks for your patience,
Please see an update on the recent issues that some users of 3rd party apps are experiencing when trying to authenticate to the API.
There are two distinct errors (below):
- "Allow Access" page not displaying correctly
This is caused by 3rd party apps using unsupported browser versions in their implementations. We have worked to quickly develop and release a patch which should mitigate the issues with the “"Allow Access” button not displaying correctly when authorising a user for an app. This patch will only fix the display issue with the "Allow Access" window and may not fix any issues with redirecting the user back to the app after authentication. These issues are due to an unsupported browser implementation, in which case the developer will need to update their app to support the latest browser version. - App unable to complete the authentication process
Some apps are using browser implementations which are no longer supported, impacting the authentication process. The developer will need to update the app to a supported browser version. MYOB recommends using the latest version of your web browser, or at least the previous version.
We apologise for the inconvenience. If you are a developer and require further assistance, please contact API support via the form below:
https://apisupport.myob.com/hc/en-us/requests/new?ticket_form_id=215283.
Trish_Lee LiamM Matiu DilipB Mike_James Illek rfeng Kerry_Busby Phil_Jeffrey_KC
MikeG1I 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.
What rubbish, how could this be marked as a solution.
Hi MikeG1 I think you need to clearly pass on to your leadership team that they have failed significantly in this matter.
Forget the 3rd party developers that have been let down and abandoned here. I think you should be more worried about the reputational damage that MYOB now have.
Our 100+ MYOB users are over the moon with us for having found a solution for something MYOB caused and then tried to pass the issue to us. Fortunately for us they are not happy with MYOB.
MYOB changed something and have caused these clients days of significant stress.
Even though we have found and implemented a fix, the software company that we have developed the link for now have to do 80 individual VM installs. At 15 minutes an install you can do the math of lost time they are facing over the next few days.
MYOV could have made one small change to allow the existing links to continue to work and then given us a clear warning that on XX date the OAuth browser method will change and provide the developers with the option.
My developer NathanCrane spend a few hours researching to find the solution and even more hours testing. This info should have been on the top of MYOB API development teams list of solutions. Hopefully that sharing this has helped a few of the other companies.
It has however not helped the reputation of MYOB in this matter.So all are clear, as the person who raisd this issue, i DO NOT accept the marked solution so I have removed that tag. So, not only do MYOB wash their hands, they now assume to speak on behalf of their users. I can assure you, you do not.
Whilst we have made the code change required, and btw MikeG1 it was I who told YOU about the software issue so even that is an epic fail from MYOB, we are still weeks away from being able to roll out as its not an internal app, its commercial software that for some strange reason we need to properly test and certify despite MYOB seemingly being able to run amok with their systems.
Disgusting.
Hi all
MYOB has posted an update today
You can read it here
For IE10 or IE11 - we have extended the support of integrations but recommend migrating off internet explorer as soon as possible.
For IE9 or lower, please update your integration immediately to enable connection to our customers ledgers
