Fix: Unsupported protocol version between an MCP client and server (2025-11-25 vs 2026-07-28)
MCP error -32022 means your client opened at 2025-11-25 but the server only serves 2026-07-28. Make one side dual-era instead of pinning a version.
Tag: errors
127 posts · Page 2 of 13
Fix: A restricted method in java.lang.System has been called in a Flutter Gradle build
The JEP 472 warning on JDK 24+ is harmless and prints once. Fix it by matching your JDK to a Gradle version that supports it, not by pasting flags into gradle.properties.
Fix: [firebase_messaging/apns-token-not-set] APNS token has not been set on Flutter iOS
getToken() runs before APNs hands iOS the device token. Poll getAPNSToken() until it returns non-null, then call getToken(). Check the Push Notifications capability if it never arrives.
Fix: Toolchain installation does not provide the required capabilities: [JAVA_COMPILER]
Gradle is compiling with a JRE. It is not searching your machine, it is using the exact JVM it was launched on. Point flutter config --jdk-dir at a real JDK, or clear org.gradle.java.home.
Fix: [FromForm] Dictionary<string, string> is always null in a minimal API
A [FromForm] Dictionary in a minimal API binds with an empty prefix: the form keys must be [key], not metadata[key]. Wrap it in a class to keep readable names.
Fix: The class 'GoogleSignIn' doesn't have an unnamed constructor
google_sign_in 7.0.0 made GoogleSignIn a singleton. Replace GoogleSignIn(scopes: ...) with GoogleSignIn.instance, await initialize() once, then call authenticate().
Fix: Unable to find a destination matching the provided destination specifier in a Flutter iOS build
iOS 26 simulator runtimes are arm64-only, so a leftover EXCLUDED_ARCHS arm64 line builds an Intel-only Runner no simulator can execute. Drop the exclusion.
Fix: "An exception was thrown while attempting to evaluate a LINQ query parameter expression" in EF Core 11
EF Core throws this when a client-evaluated piece of your query throws while EF evaluates it. Read InnerException, turn on EnableSensitiveDataLogging, and move the null check outside the lambda.
Fix: cannot target OpenAPI 3.0 after upgrading Swashbuckle.AspNetCore to v9
Swashbuckle 8 and later emit openapi 3.0.4, not 3.0.1, and there is no OpenApiSpecVersion for a patch version. Why it changed, and four ways to pin the string your tooling expects.
Fix: Swagger UI shows Unable to render this definition after upgrading to .NET 11
ASP.NET Core 11 emits openapi 3.2.0 by default and Swagger UI below 10.1.5 rejects it. Upgrade Swashbuckle.AspNetCore.SwaggerUI, or pin OpenApiVersion back to OpenApi3_1.