Skip to main content
Support Center
Help ArticlesAcademyCommunity
HomeCommunitySDK/APIOther/GeneralGetting PlatformNotSupportedException when authenticating to GeoTab

Getting PlatformNotSupportedException when authenticating to GeoTab

Open
SDK/API
Other/General
M
M
mdevol
Original Poster

I'm trying to upgrade the Geotab.Checkmate.ObjectModel nuget package from ver 11.118.421 to ver 11.132.485. However, when I try to run my application after upgrading, I get the following runtime error when authenticating (AuthenticateAsync()) to Geotab:

System.PlatformNotSupportedException: Operation is not supported on this platform.
at System.Net.Http.HttpClientHandler.set_CheckCertificateRevocationList(Boolean value)
at Geotab.Checkmate.Web.HttpMessageHandlerBuilder.PropertySetter.SetCheckCertificateRevocationList(HttpMessageHandler& httpMessageHandler, Nullable`1& value)
at Geotab.Checkmate.Web.HttpMessageHandlerBuilder.Build()
at Geotab.Checkmate.Web.WebServerInvoker.CreateSharedHttpClient()
at Geotab.Checkmate.Web.WebServerInvoker..cctor()


As I understand this error message, a newer version of the .NetFramework is needed than what the application is running, which in my case is 4.6.2. Could you please let me know what is the minimum supported .NetFramework version for the latest version of Geotab.Chackmake.ObjectModel.

10
Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

10 Replies

E
E
EishiFUN
Community Administrator

Hey @mdevol ,

Thank you for bringing this up in our community. I talked to our dev team and this was not expected to happen. I thought at first when I looked at this page: https://www.nuget.org/packages/Geotab.Checkmate.ObjectModel#readme-body-tab That you needed to be on .net 8 but when I talked to the dev they told me "The nuget package is supposed to support .net framework, they don't necessarily "need" to be on .net 8"

We have opened a dev ticket MYG-138208 for you reference to look into this more. I will let you know what I hear from that investigation as soon as I do. If there is more information we need or anything I will reach out.

Have a great day!
Eishi FUN

M
M
mdevol
Original Poster

@EishiFUN Thanks, I have a very small test app that reproduces this problem if it would be helpful. If you're interested in it, just let me know where to send it.

E
E
EishiFUN
Community Administrator

Thank you I appreciate it @mdevol. We were also able to reproduce it when we tested it

M
M
mdevol
Original Poster

Any idea when there will be a new release to fix this issue?

E
E
EishiFUN
Community Administrator

Edited by EishiFUN

@mdevol I got a response from our team today about this: "The minimum .net framework version needed is 4.7.2. The user can update to that version to stop getting the exception. If they do not want to upgrade - we will have a fix ready by next week."

M
M
mdevol
Original Poster

@EishiFUN Thanks for the update. I tried to update our project to 4.7.2, but couldn't get it build for non-GeoTab reasons. So, we're holding at 4.6.2 for now. I'll keep an eye out for the fix next week.

E
E
EishiFUN
Community Administrator

@mdevol Hey I did get an update that there is a myG update they are waiting on so this will be held up until next Tuesday. If I hear anything else I will let you know.

M
M
mdevol
Original Poster

@EishiFUN Ok, thanks

M
M
mdevol
Original Poster

@EishiFUN I got the latest GeoTab package that was released on Monday and was able to apply to our code with no issues. So consider this closed. Thanks for the help,

E
E
EishiFUN
Community Administrator

@mdevol Hey thanks a lot for following up! I am glad this ended up working. Thank you for being patient with us and bringing it up here in the community.

Pease reach out any time you have questions. We are always happy to help

Still have questions?
Learn with AcademyBrowse documents