-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception after "checking for new navigation data" #135
Comments
Is that the entirety of the exception stack trace? |
I believe so. Let me ask him
…________________________________
From: Justin Shannon ***@***.***>
Sent: Tuesday, May 9, 2023 6:11:10 AM
To: vatis-project/vatis ***@***.***>
Cc: Neil Enns ***@***.***>; Author ***@***.***>
Subject: Re: [vatis-project/vatis] Exception after "checking for new navigation data" (Issue #135)
Is that the entirety of the exception stack trace?
—
Reply to this email directly, view it on GitHub<#135 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACIVHFTH73RHAN4TT2LGEATXFI665ANCNFSM6AAAAAAX2HY2NI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
He says yes, the rest was just version info for the assemblies, but will get me the entire thing in a day or two (he's away from his computer for the next few days). |
In beta 13, the HttpClient is forced to use IPv4, which will hopefully fix this issue. I'm theorizing that the user is getting the |
I let him know. He likely won't be able to try it for another day or so, but I'll report back once I hear results. |
Seems like that change fixed it:
|
This is happing to a fellow controller. On launch of vATIS he gets the "checking for new navigation data" message and then the app crashes:
Log file contents:
We've tried uninstalling and nuking the
vATIS-4.0
folder from%localappdata%
on his machine then reinstalling beta 12 but the exception still happens.The text was updated successfully, but these errors were encountered: