🐛 Bug Report: Signup is not working Network error

[rajesh-avula]

👟 Reproduction steps

1. Go to signup page
2. Enter the details and click on signup.
3. It's throwing Network error

Note : Before upgrading to angular v13 it was working as expected.

👍 Expected behavior

User should be able to signup and login

👎 Actual Behavior

User is not able to signup as it's displaying network error

🎲 Appwrite version

Version 0.10.x

💻 Operating system

Windows

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[gewenyu99]

@brandonroberts has updated the app. This issue should be fixed now!

Please clear cache and try again, let us know if it's still a problem :)

[jwetzell]

Signup still seems to be an issue. This section of the Account.Signup account seem to be incorrect. Lines 97-101

let account = await Api.provider().account.create(
        email,
        password,
        name
);

the node library was updated back in January to reflect a change in the API where a userId can be provided so the account.create now takes (userId, email, password, name) adding 'unique()' for the userId per the API documentation will just generate an ID so the call would look like

let account = await Api.provider().account.create(
       'unique()',
        email,
        password,
        name
);

[brandonroberts]

@jwetzell yep, that's true. Must have missed that one in the update. Would you like to put in a PR to fix?

[jwetzell]

@brandonroberts Yeah I can put in a PR. Is just using the string 'unique()' alright for this demo app?

[brandonroberts]

@jwetzell Great! Yep, that's fine

[jwetzell]

@brandonroberts No problem, PR opened. I didn't reference this issue as not really sure this is the problem this issue was originally about. But I didn't experience any problems with signup after correcting this call.

[brandonroberts]

No problem. Might have been an isolated issue, but will be resolved with the PR either way 🙂