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

Always getting "something went wrong" error on auth0 branding texts update signup command #515

Closed
6 tasks done
maggie9595 opened this issue Nov 8, 2022 · 9 comments
Closed
6 tasks done
Labels
bug This points to a verified bug in the code

Comments

@maggie9595
Copy link

maggie9595 commented Nov 8, 2022

Checklist

  • I have looked into the README and have not found a suitable solution or answer.
  • I have looked into the documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have upgraded to the latest version of this project and the issue still persists.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

Description

The same auth0 branding texts update signup command that we are running for our tenants in version 0.11.7 seems to be erroring out persistently after we updated to version 0.12.0, with this error:

!!     Uh oh. Something went wrong.
!!     If this problem keeps happening feel free to report an issue at
!!
!!     https://github.com/auth0/auth0-cli/issues/new/choose

Reinstalling did not seem to fix the error either.

Expectation

auth0 branding texts update signup should not error out in the new version of the CLI.

Reproduction

  • Update to newest version (0.12.0) of the CLI
  • Try to run auth0 branding texts update signup command on any tenant
  • Get persistent something went wrong error

Auth0 CLI version

0.12.0

@maggie9595 maggie9595 added the bug This points to a verified bug in the code label Nov 8, 2022
@jdk2pq
Copy link

jdk2pq commented Nov 8, 2022

I'm having the same issues with any auth0 branding texts update command. Every prompt I've tried gives the above error, except for auth0 branding texts update login.

@maggie9595 maggie9595 changed the title Always getting "something went wrong" error on auth0 branding texts show signup command Always getting "something went wrong" error on auth0 branding texts update signup command Nov 9, 2022
@maggie9595
Copy link
Author

I'm having the same issues with any auth0 branding texts update command. Every prompt I've tried gives the above error, except for auth0 branding texts update login.

This is actually the case for me as well, just updated my issue!

@jameskyker
Copy link

jameskyker commented Dec 7, 2022

Auth0's API is broken. We tried to issue the GETs described here, and none of them seem to work except for login. The login prompt returns values, but signup, for instance, returns an empty object as well as every other prompt we tried. Auth0 needs to fix their API, and then this client will probably work.

@jameskyker
Copy link

Never mind. We did some additional testing today, and the GETs aforementioned return an empty object when there is no customization. Once we customized a few fields via the API, the GET is returning data. Therefore, the API is not busted as I stated. The client is. Sorry for the distraction here.

@willvedd
Copy link
Contributor

willvedd commented Jan 5, 2023

Hi folks, appreciate everyone's feedback and patience. I've confirmed that all invocations of the auth0 branding texts update with a non-login prompt type result in an error. It appears that there is some faulty logic when trying to seed default branding texts to the editor.

I have PR up to fix this issue, however it'll be gated behind our v1 branch. What this means is that this fix won't be released until our first major release. We're targeting the next few weeks for beta and GA in mid-February; it's something we're very excited about. We acknowledge the wait and appreciate everyone's patience until then. I will be providing further updates as these releases go out.

@willvedd
Copy link
Contributor

Update: We've included fix for this in the v1.0.0-beta.1 release. For those who are so inclined, we'd be happy to receive feedback on the beta before it goes GA, including feedback on this particular issue. Otherwise, we plan to close this issue out once v1.0.0 reaches GA. Again, appreciate everyone's patience!

@smart
Copy link

smart commented Apr 8, 2023

I downloaded the 1.0 beta3 and tried this command and still got the invalid memory issue

./auth0 universal-login templates update
⣽panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x105404998]

goroutine 25 [running]:
github.com/auth0/auth0-cli/internal/cli.fetchBrandingSettingsOrUseDefaults({0x105b4fcd0?, 0x1400070e0f0}, 0x1400044e000)
/home/runner/work/auth0-cli/auth0-cli/internal/cli/universal_login_templates.go:292 +0x1b8
github.com/auth0/auth0-cli/internal/cli.(*cli).fetchTemplateData.func4()
/home/runner/work/auth0-cli/auth0-cli/internal/cli/universal_login_templates.go:223 +0x34
golang.org/x/sync/errgroup.(*Group).Go.func1()
/home/runner/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:75 +0x5c
created by golang.org/x/sync/errgroup.(*Group).Go
/home/runner/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:72 +0x9c

@willvedd
Copy link
Contributor

Hi all, the fix for this issue (including @smart 's point) has been released with v1.0.0. We hope that everyone upgrades and gives it a shot!

@maggie9595
Copy link
Author

Hi all, the fix for this issue (including @smart 's point) has been released with v1.0.0. We hope that everyone upgrades and gives it a shot!

Thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This points to a verified bug in the code
Projects
None yet
Development

No branches or pull requests

5 participants