Error Connecting Windows App to MYOB

Hi @Mike_MYOB

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 everyone, I wanted to highlight some brilliant support from @Steve_PP that has already helped other developers to overcome this.
Please check out their post here which includes example code and instructions.
Thank you Steve!

SteveP1

Hi @DevRBSystems

You seem to be on the right track, but I don't see where you parse "code=..." from the "https://desktop?code=..." URL. It looks like you are treating it like a "normal" URL and opening it in the browser.

The "desktop" URL is what MYOB call the "Redirect URL", which is used to get back to your application after going through the MYOB login screens. When you get the "desktop" URL, instead of browsing to it (which gives the error you posted), you parse the URL to get the "code" value, which is used in subsequent communication with MYOB.

Your screenshot shows the "code" in the redirect URL, @Phil_Jeffrey_KC posted an answer that might help you here.

See also this question Getting OAuth code when Redirect is http://desktop

DevRBSystems

Hi All,
I've been working though this for several days and I've built a test app (i've built this using example code from the community) using the WebView2 package and still no luck.

Even when I try using Edge I still get an error message as below:

Other times I get and IP Address error message.

I'm trying this on my Dev and other device with the same results, the best I've had so far is edge in that it gave me back a code.

I have tried my test app and I've only ever got back a response with the code in it and off course it had an error.

Below is the code for the form as I can't add the project files....

Imports Microsoft.Web.WebView2.Core
Imports System.IO

Public Class frmWebView
Private Async Sub frmWebView_Load(sender As Object, e As EventArgs) Handles MyBase.Load
txtURL.Text = "https://www.google.com.au"
LogMsg($"MS Edge Version: {CoreWebView2Environment.GetAvailableBrowserVersionString()}")
' Initialise.
Await wvwMain.EnsureCoreWebView2Async()
'Await InitializeCoreWebView2Async(Path.Combine("C:\Temp", Reflection.Assembly.GetExecutingAssembly().GetName().Name))

If Not String.IsNullOrEmpty(txtURL.Text) Then
' Navigate to URL.
WebsiteNavigate(txtURL.Text)
End If
End Sub

Private Sub frmWebView_FormClosed(sender As Object, e As FormClosedEventArgs) Handles MyBase.FormClosed
' Unsubscribe from CoreWebView2 event(s) (remove event handlers).
RemoveHandler wvwMain.CoreWebView2.HistoryChanged, AddressOf wvwMain_HistoryChanged
End Sub

Private Sub txtURL_KeyPress(sender As Object, e As KeyPressEventArgs) Handles txtURL.KeyPress
'// Press ENTER
If Asc(e.KeyChar) = 13 Then
'// No beep
e.Handled = True
Try
'wvwMain.CoreWebView2.Navigate(txtURL.Text)
'// Or --> wvwMain.CoreWebView2.Navigate(txtURL.Text)
wvwMain.Source = New Uri(txtURL.Text)
Catch ex As UriFormatException
MessageBox.Show("The URL must be fully styled, such as the prefix. http[s]://")
Catch ex As Exception
MessageBox.Show($"Error: {ex}")
End Try
End If
End Sub

Private Sub wvwMain_CoreWebView2InitializationCompleted(sender As Object, e As CoreWebView2InitializationCompletedEventArgs) Handles wvwMain.CoreWebView2InitializationCompleted
LogMsg("wvwMain_CoreWebView2InitializationCompleted")
LogMsg($"UserDataFolder: {wvwMain.CoreWebView2.Environment.UserDataFolder.ToString()}")
' Subscribe to CoreWebView2 event(s) (add event handlers).
AddHandler wvwMain.CoreWebView2.HistoryChanged, AddressOf wvwMain_HistoryChanged
End Sub

Private Sub wvwMain_NavigationCompleted(sender As Object, e As CoreWebView2NavigationCompletedEventArgs) Handles wvwMain.NavigationCompleted
MessageBox.Show(wvwMain.Source.ToString())
LogMsg("wvwMain_NavigationCompleted")
End Sub

Private Sub wvwMain_WebMessageReceived(sender As Object, e As CoreWebView2WebMessageReceivedEventArgs) Handles wvwMain.WebMessageReceived
LogMsg("wvwMain_WebMessageReceived")
End Sub

Private Async Function InitializeCoreWebView2Async(Optional userDataFolder As String = "") As Task
Dim options As CoreWebView2EnvironmentOptions = Nothing
Dim cwv2Environment As CoreWebView2Environment = Nothing

' It's recommended to create the userDataFolder in the same location
' that your other application data is stored (ie: in a folder in %APPDATA%)
' if not specified, we'll create a folder in %TEMP%
If String.IsNullOrEmpty(userDataFolder) Then
userDataFolder = Path.Combine(Path.GetTempPath(), Reflection.Assembly.GetExecutingAssembly().GetName().Name)
End If

' Create WebView2 Environment using the installed or specified WebView2 Runtime version.
'cwv2Environment = Await CoreWebView2Environment.CreateAsync("C:\Program Files (x86)\Microsoft\Edge Dev\Application\1.0.1054.31", userDataFolder, options)
cwv2Environment = Await CoreWebView2Environment.CreateAsync(Nothing, userDataFolder, options)
' Initialise.
Await wvwMain.EnsureCoreWebView2Async(cwv2Environment)
End Function

Private Sub wvwMain_HistoryChanged(sender As Object, e As Object)
LogMsg("wvwMain_HistoryChanged")
'btnBack.Enabled = WebView21.CoreWebView2.CanGoBack
'btnForward.Enabled = WebView21.CoreWebView2.CanGoForward
' Update the Address Bar.
UpdateAddressBar()
End Sub

Private Sub LogMsg(msg As String, Optional addTimestamp As Boolean = True)
If addTimestamp Then
msg = $"{Now.ToString("yyyy/MM/dd HH:mm:ss.fff")} - {msg}"
End If

Debug.WriteLine(msg)
End Sub

Private Sub UpdateAddressBar()
'' If necessary, update address bar.
'If textBoxAddressBar.Text <> wvwMain.Source.ToString() Then
' textBoxAddressBar.Text = wvwMain.Source.ToString()

' 'move cursor to end of text
' textBoxAddressBar.SelectionStart = textBoxAddressBar.Text.Length
' textBoxAddressBar.SelectionLength = 0
'End If
End Sub

Private Sub WebsiteNavigate(ByVal dest As String)
If wvwMain IsNot Nothing AndAlso Not String.IsNullOrWhiteSpace(dest) Then
' URL must start with one of the specified strings
' if Not, pre-pend with "https://"
If Not dest = "about:blank" AndAlso Not dest.StartsWith("edge://") AndAlso
Not dest.StartsWith("file://") AndAlso Not dest.StartsWith("http://") AndAlso
Not dest.StartsWith("https://") AndAlso
Not System.Text.RegularExpressions.Regex.IsMatch(dest, "^([A-Z]|[a-z]):") Then
' Set Value
dest = "https://" & dest
End If

' Option 1.
'wvwMain.Source = New Uri(dest, UriKind.Absolute)
' Option 2.
wvwMain.CoreWebView2.Navigate(dest)
' Update the Address Bar.
UpdateAddressBar()
End If
End Sub
End Class

Please let me know what I am doing wrong here.

Hi @NathanCrane Thank you for this update. It helped us to find the solution. Really appreciate you sharing this information.

Matt_Sawyer

What rubbish, how could this be marked as a solution.

Phil_Jeffrey_KC

@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". @Mike_MYOB , can you confirm if "http://desktop" is still valid as the redirect URI?

@Mike_MYOB

Hi Mike,

How can this be marked as a solution; it certainly is not a solution.

This is great to hear @NathanCrane , thank you for sharing, hopefully this is helpful to others who are having this issue. Thanks!

NathanCrane

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 @DilipB

We are still investigating what can be done, unfortunately it will take us at least several weeks for a solution, I am hoping that MYOB has a better answer tomorrow.

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.

LiamM

@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?

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

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:

Phil_Jeffrey_KC

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.

Sorry its taking a little longer than expected. Want to make sure the information is correct and clear for the update to you all

Kerry_Busby

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.

@Trish_Lee @LiamM @Matiu @DilipB @Mike_James @Illek
I will have an update for you in the next 30mins with some more information - thanks MG

Mike_James

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.

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

@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.

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

Matiu

Can you provide an optional rollback of yesterday’s update? This is going to cause a lot of short term pain.

@Mike_MYOB

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

LiamM

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 @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

@LiamM @Mike_MYOB

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

Not yet sorry @Matiu - if I find out more, I will aim to update some of the posts in the forum here

Hi @DilipB , its unrelated to the 2024.7 AccountRight release, but we think it could be related to some other changes that happened relating to Auth. The team are investigating. If you submit a support ticket via developer.myob.com you will be able to receive updates from there.