Always getting "something went wrong" error on `auth0 branding texts update signup` command about auth0-cli HOT 9 CLOSED

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.

from auth0-cli.

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.

from auth0-cli.

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.

from auth0-cli.

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!

from auth0-cli.

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!

from auth0-cli.

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.

from auth0-cli.

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

from auth0-cli.

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!

from auth0-cli.

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!!

from auth0-cli.