Flutter Windows App for AppSync - CERTIFICATE_VERIFY_FAILED

[jobypthomas]

Description

I built a flutter app few years ago with Amplify to glue the AWS backend. I have iOS, Android, Web and Windows apps. All of them were working just fine. However, I started getting the following error in ONLY Windows App about a month ago:
flutter: UnknownException {
"message": "unable to send GraphQLRequest to client.",
"underlyingException": "POST https://xxxxxxxxxxxxxxxxx.appsync-api.us-east-1.amazonaws.com/graphql/ failed: HandshakeException: Handshake error in client (OS Error: \n\tCERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate(../../third_party/boringssl/src/ssl/handshake.cc:393))"
}
The requests fails for local certs and also for the Microsoft issued certificates for Windows App Store.
Authentication works (Cognito) just fine. It is the GQL API requests that fails. I use msix for signing (https://pub.dev/packages/msix)
Anyone?
Dart packages
msix | Dart package

Categories

• Analytics
• API (REST)
• API (GraphQL)
• Auth
• Authenticator
• DataStore
• Notifications (Push)
• Storage

Steps to Reproduce

Login using the App (Auth services works just fine)
The data is fetched and instead raised the error:
flutter: UnknownException {
"message": "unable to send GraphQLRequest to client.",
"underlyingException": "POST https://xxxxxxxxxxxxxxxxx.appsync-api.us-east-1.amazonaws.com/graphql/ failed: HandshakeException: Handshake error in client (OS Error: \n\tCERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate(../../third_party/boringssl/src/ssl/handshake.cc:393))"
}

Screenshots

No response

Platforms

• iOS
• Android
• Web
• macOS
• Windows
• Linux

Flutter Version

3.7.0

Amplify Flutter Version

12.4.0

Deployment Method

Amplify CLI (Gen 1)

Schema

No response

[jobypthomas]

I noticed similar issue but with a different category - #4161
@BeamTrakLLC

[ekjotmultani]

Hi @jobypthomas, thanks for taking the time to raise this issue, I'm sorry that you are facing this. We will investigate and attempt to reproduce this issue, will get back to you with an update when we have one

[NikaHsn]

@jobypthomas I think this is duplicate of #4714. if so please follow #4714 for update.