-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Breaking change introduced when upgrading from 6.6.5 to 6.6.6 #14051
Comments
Hey @ffxsam, thanks for raising this issue. We will investigate and follow up |
Hi @ffxsam, while we are investigating, can you try to clear your node_modules & lock file to ensure there are no competing installations of core dependencies causing this conflict? |
Hey @jjarvisp! No such luck after removing |
Looking at your environment details you have this:
I checked the deps tree of Are you listing |
Ah! We were able to finally update this code: import { generateClient } from 'aws-amplify/api';
import type {
GraphQLResult,
GraphQLSubscription,
} from '@aws-amplify/api-graphql'; because older versions of import {
generateClient,
type GraphQLResult,
type GraphQLSubscription,
} from 'aws-amplify/api'; Glad that was super easy! Thanks for your help! |
Before opening, please confirm:
JavaScript Framework
Vue
Amplify APIs
GraphQL API
Amplify Version
v6
Amplify Categories
api
Backend
Other
Environment information
Describe the bug
Since upgrading from
aws-amplify
6.6.5 to 6.6.6, we're seeing warnings/errors that are breaking our application with no code changes on our end.[WARN] 47:16.660 GraphQLAPI resolveConfig - The API configuration is missing. This is likely due to Amplify.configure() not being called prior to generateClient().
error-reporter.ts:14 NoValidAuthTokens: No federated jwt
Subscribe only available for AWS AppSync endpoint
Our
Amplify.configure()
call is called immediately insrc/main.ts
via an import:And that module calls
Amplify.configure()
in the global scope, not in any sort of closure.Expected behavior
I wouldn't expect any breaking changes, since this is a patch release. I looked at the release notes and didn't see anything major.
Reproduction steps
Could not offer a repo without sharing our codebase.
Code Snippet
No response
Log output
aws-exports.js
No response
Manual configuration
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
See below. Line 33 in main.ts is a call to use Vue Router, which happens long after we import
./init/amplify
.The text was updated successfully, but these errors were encountered: