🐛 Bug Report: accounts.create does not get trigger function on account created with OAuth provider

[matfire]

trafficstars

👟 Reproduction steps

• Create a function that should get triggered on accounts.create
• Deploy tag (my use case was creating a document in a collection)
• Create an account with email and password from a web frontend (React in my specific case)
• Function should get triggered
• Create another account using an Oauth provider (Google in my case)
• Function should not get triggered

👍 Expected behavior

Function should get triggered in both cases, when an account is created using email + password and when using a third party provider (Google, Github etc)

👎 Actual Behavior

Function gets triggered only when creating an account using email and password

🎲 Appwrite version

Different version (specify in environment)

💻 Operating system

Linux

🧱 Your Environment

Appwrite v:0.11.0.170

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

• [X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

[JaviBonilla]

I’m also having the same issue.

[PineappleIOnic]

I'm on the case 👍

[garvitomer]

Is this issue solved in 13.4 or it is still there? Last I checked it was there in 12.x versions

[PineappleIOnic]

@TorstenDittmann Was this fixed in 0.14 with the new Event model?

[stnguyen90]

@PineappleIOnic, looking at the code, it looks like the user is created, but no new user event is triggered:

https://github.com/appwrite/appwrite/blob/648b6f2038fb59b2beb78d81cea08aa730a106c3/app/controllers/api/account.php#L466-L501

[karniv00l]

I think this issue also exists when creating a user using Magic URL

[ddenev]

@stnguyen90 , can this be prioritized higher?

I see this has been lagging since 0.16 milestone but currently this bug prevents me from using Google OAuth2 in my app.

Thank you!

[garvitomer]

Use 'session.create' for time being, I am also using the same.

On Sun, 9 Oct, 2022, 1:58 pm Dragomir Denev, @.***> wrote:

@stnguyen90 https://github.com/stnguyen90 , can this be prioritized higher?

I see this has been lagging since 0.16 milestone but currently this bug prevents me from using Google OAuth2 in my app.

Thank you!

— Reply to this email directly, view it on GitHub https://github.com/appwrite/appwrite/issues/2406#issuecomment-1272487880, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASHUZ2C6FON4AKHHFK5ULULWCJ62NANCNFSM5H2GGTHA . You are receiving this because you commented.Message ID: @.***>

[t0mm4rx]

Still an issue with Magic URLs. Checking for session creation with some sort of state is possible but not ideal.

[moshOntong-IT]

What is the status for this issue?

[moshOntong-IT]

We should consider introducing a new method named createOAuth2.

The primary objective of this method is to facilitate sign-up using an OAuth2 provider. When this method is invoked, the backend will recognize the user as a new one, subsequently triggering the appropriate event.

On the other hand, the existing method, createOAuth2Session, is solely for signing in or establishing a session with the OAuth provider. If the account does not exist, it should return a "404 Not Found" error, rather than automatically creating a new account.

[PratikDev]

Hey, what's the status of this issue?

[tdansie]

Also checking in on the status so that we can implement Google oauth. Is there a work around at the moment?

[ItzNotABug]

Subscribing to this.

[limes]

Hey, is it fixed in 1.5?