-
Notifications
You must be signed in to change notification settings - Fork 822
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
Question about amplify pull parameters #13344
Comments
Hey @jeremymtx, thank you for reaching out. Could you run the pull command with the |
Here it is with --debug: PS C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner> amplify pull --debug --appId d1pej0nhgss3ma --envName dev Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/ PullBackendFault: Failed to pull the backend. C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner\C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner\src contains invalid WIN32 path characters. Session Identifier: 31c196ce-0093-4958-94c7-a16cc6e73a89 PS C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner> dir
Mode LastWriteTime Length Name d---- 10/18/2023 12:56 PM .vscode PS C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner> dir src
Mode LastWriteTime Length Name d---- 10/18/2023 12:48 PM assets Prior to running the pull, I had executed the command npm create vuetify and then npm install. I thought this created the vue framework. |
Seeing the contains invalid WIN32 path characters in the exception above, I re-ran the command with the C: removed in the source directory path and had the output below. Maybe it's okay now? I am not sure if I need to pay attention to the Not pulling components...not configured with the "react" framework. It's not set up with react. PS C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner> amplify pull --debug --appId d1pej0nhgss3ma --envName dev
Edit your schema at C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner\amplify\backend\api\jpmeventplanner\schema.graphql or place .graphql files in a directory at C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner\amplify\backend\api\jpmeventplanner\schema ✅ Successfully pulled backend environment dev from the cloud. Not pulling components because this project is not configured with the "react" framework. |
Hey @jeremymtx, if you are running the command in the root of the directory that has your framework configured, you can just pass in |
Closing due to inactivity |
|
Amplify CLI Version
12.7.0
Question
I am trying to pull my app into a non-OneDrive folder as suggested in 13336. However, the pull failed. Here is the output:
PS C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner> amplify pull --appId d1pej0nhgss3ma --envName dev
Opening link: https://us-east-1.admin.amplifyapp.com/admin/d1pej0nhgss3ma/dev/verify/?loginVersion=1
⠦ Confirm login in the browser or manually paste in your CLI login key:
Successfully received Amplify Studio tokens.
Amplify AppID found: d1pej0nhgss3ma. Amplify App name is: jpmeventplanner
Backend environment dev found in Amplify Console app: jpmeventplanner
? Choose your default editor: Visual Studio Code
√ Choose the type of app that you're building · javascript
Please tell us about your project
? What javascript framework are you using vue
? Source Directory Path: C:\programming\aws\workshops\serverlessWebApp\jpm-event-planner\src
? Distribution Directory Path: dist
? Build Command: npm.cmd run-script build
? Start Command: npm.cmd run-script serve
🛑 Failed to pull the backend.
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: 9ca0fc3d-88d5-4183-a89a-188c953d03d5
I'm not sure whether what I entered for Distribution Directory Path, Build Command, and Start Command were correct. I just took the suggested defaults even though I had been executing "npm run dev" in the app's previous OneDrive location. I went to the troubleshooting link, but the only help there about pull was about failures with a large number of UI components. That's not my problem.
Any thoughts about this would be appreciated. Thanks.
The text was updated successfully, but these errors were encountered: