Skip to content
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

template.substituteValues is not a function error when performing a push using latest amplify version #13516

Closed
2 tasks done
vantablanta opened this issue Jan 5, 2024 · 3 comments
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-push Issues related to `amplify push`

Comments

@vantablanta
Copy link

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v20.10.0

Amplify CLI Version

12.10.0

What operating system are you using?

MacOs

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Just did an amplify push using the latest version of amplify cli.

Describe the bug

So we noticed this issue a while back when we upgraded the amplify cli version to 12.3.0. At the time we had node v18. We couldn't perform any push or pull. We always got template.substituteValues is not a function and the operation would fail. We rolled back to the amplify cli version that was initially working v12.0.3. We've been using this version since.

Checking back now, months later, and it seems issue is still there in the latest version of amplify ?

Expected behavior

I expected to not get a console error when performing a push locally using the latest amplify cli version.

Reproduction steps

Upgrade amplify cli to the latest version.

Try perform a push.

Project Identifier

No response

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@vantablanta vantablanta added the pending-triage Issue is pending triage label Jan 5, 2024
@ykethan
Copy link
Member

ykethan commented Jan 5, 2024

Hey @vantablanta, thank you for reaching out. Could you provide us some additional information on the error message, by running amplify push with --debug.
Does the error occur when running push on a resource such as custom/overrides?
could you run amplify diagnose --send-report and provide us the Project Identifier output from the terminal.

@ykethan ykethan added pending-response Issue is pending response from the issue author platform-push Issues related to `amplify push` labels Jan 5, 2024
@josefaidt
Copy link
Contributor

Closing due to inactivity

@josefaidt josefaidt closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2024
Copy link

github-actions bot commented Feb 2, 2024

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-push Issues related to `amplify push`
Projects
None yet
Development

No branches or pull requests

3 participants