Inline suggestions gone quiet on your Swift files? Work through sign-in, settings, file context, and network causes to get Amazon Q Developer completing again.
When Amazon Q Developer stops offering inline suggestions, it is almost always a configuration or connection issue rather than a broken product.
Inline completion depends on a chain: you must be signed in, the feature must be enabled, the file must be in a real project, and the extension must reach the cloud service.
Break in any link and the ghost-text suggestions simply stop appearing, often with no obvious error.
This guide walks the chain from most to least common cause, so work through it in order rather than jumping around.
One reassurance first. Swift is a supported language, so if you were getting suggestions before and they vanished, the language is not the problem — something in that chain changed, and the steps below find it.
The single most common cause is a lapsed or incomplete sign-in.
Open the Amazon Q panel from the VS Code sidebar and look at the account state. If it prompts you to sign in, your previous session expired, which happens periodically.
Sign in again using your Builder ID or your organization's IAM Identity Center, and complete the confirmation step in the browser. Do not assume it worked until the panel clearly shows a signed-in state.
If sign-in seems to complete but the panel still looks logged out, sign out fully and back in to reset the token.
Once authenticated, open a Swift file and type a few lines to see whether suggestions return. A surprising share of missing-suggestion reports are resolved at exactly this step, so do not skip it.
If you are signed in but still see nothing, the feature itself may be turned off.
Open VS Code Settings and search for Amazon Q. Look for the inline suggestion or code completion toggle and make sure it is enabled.
Also check whether you or a keyboard shortcut paused suggestions. Some workflows pause completion to reduce distraction, and it is easy to forget it is off.
While you are there, confirm no other completion extension is conflicting. Two AI assistants both trying to show inline text can cause one to appear to do nothing.
After changing a setting, it can help to reload the VS Code window so the extension picks up the new state cleanly. Then test again in a Swift file before moving on.
Context matters, and a single orphaned file gives the assistant little to work with.
Make sure you opened your project with File then Open Folder, pointing at the project root, rather than opening one Swift file in isolation.
With the whole folder open, Q can use surrounding files as context, which both improves suggestion quality and, in some cases, makes suggestions appear at all.
Confirm the file you are editing actually has a .swift extension and is recognized by VS Code as Swift. The language mode is shown in the status bar and can occasionally be wrong for unusual setups.
Give the assistant something to complete. On a nearly empty file it may stay quiet, so start a function or write a descriptive comment, then pause and let it propose the next lines.
Amazon Q generates suggestions in the cloud, so it needs a working connection.
Check that you have general internet access, and if you are on a corporate network, VPN, or behind a proxy, be aware these often block or interfere with the service.
If other cloud tools also misbehave, the network is the likely culprit. Try a different network to isolate the issue quickly.
Corporate proxies sometimes require configuration for the extension to reach AWS endpoints. If that is your environment, check with your IT team about allowed domains and proxy settings.
After any network change, reload VS Code and re-check the sign-in state, since a dropped connection can also silently invalidate your session. Restoring connectivity often brings suggestions straight back.
A stale or corrupted extension install is a less common but real cause.
Open the Extensions view, find Amazon Q, and check for an available update. Install any pending update, since fixes ship regularly.
If you are already current, try disabling and re-enabling the extension, then reload the window.
When problems persist, uninstall the extension, restart VS Code fully, and reinstall it from the official AWS publisher. This clears out a bad local state more reliably than a simple toggle.
Also confirm your VS Code itself is reasonably up to date, because very old editor versions can be incompatible with current extensions. A clean, current install removes a whole class of hard-to-diagnose issues.
When the obvious fixes fail, the extension's own logs usually point at the cause.
Open the VS Code Output panel and select the Amazon Q channel from the dropdown. Errors about authentication, network, or the service surface here in plain text.
An authentication error confirms you should redo sign-in. A network or timeout error points back to connectivity and proxy checks.
Copy any error message and search the official documentation or paste it into Q chat if chat still works, which is a fast route to a specific fix.
Logs turn guesswork into diagnosis. Rather than randomly toggling settings, let the output channel tell you which link in the chain is actually broken, then apply the matching fix above.
If you have worked through every step and Swift suggestions are still absent, step back and sanity-check the basics.
Confirm the service is not experiencing an outage by checking AWS status and the official channels, since an occasional service-side issue is out of your hands.
Try a brand-new empty project with a simple Swift file. If suggestions work there, the problem is specific to your project's setup, which narrows the hunt considerably.
Remember what suggestions are and are not. Even when working perfectly, inline completion assists your typing; it does not build or run your iOS app, which happens in Xcode.
Most missing-suggestion cases come down to sign-in, an off toggle, or the network, and walking the chain in order resolves the large majority. When it does not, the logs and a clean test project will tell you where to look next.
Most often your sign-in session expired. Open the Amazon Q panel, confirm the account state, and sign in again with Builder ID or IAM Identity Center, completing the browser confirmation.
Yes, Swift is supported. If suggestions vanished after working before, the language is not the issue — check sign-in, the inline completion setting, project context, and your network.
Yes. Amazon Q generates suggestions in the cloud, so VPNs and proxies can block it. Try a different network to isolate the problem, and ask IT about allowed AWS domains if needed.
Open the VS Code Output panel and select the Amazon Q channel. Authentication, network, or service errors appear there in plain text and point you to the right fix.
That is expected. Amazon Q only assists authoring. Building and running your iOS app happens in Xcode, which reads the same files you edit in VS Code.