Hi again! I'm trying to to do signinup with apple, as I have google working. When I do the same with Apple, it throws an error on the backend.

javascript
console.log(credential.authorizationCode);

      await axios
        .post(
          `${API_DOMAIN}/auth/signinup`,
          {
            redirectURI: "com.demoapp:/oauthredirect",
            thirdPartyId: "apple",
            code: credential.authorizationCode,
            clientId: MY CLIENT ID.
          },
          {
            headers: {
              rid: "thirdpartyemailpassword",
            },
          }
        )

@nkshah2 can help with this.

Thank you!

Hey @killian.s can you print the full response you received from the signinup API?

.catch((error) => { console.log(error.response); }); console.log(result); Is that what you are looking for?

Yep can you also print the full request body

On the server?

Or on the client, either works

I think that is it

Is the client id for a service id or an app id on the apple developer portal?

I think it's for the app

Can you click on the edit button next to sign in with apple

Also got it as a key

Right so in our example app: https://github.com/supertokens/supertokens-react-native/blob/master/examples/with-thirdpartyemailpassword/apple.js We use the key configuration as the client id for iOS (The AppId flow only works for iOS and other apple platforms)

let signInUpResponse = await axios.post(
            `${API_DOMAIN}/auth/signinup`,
            {
                redirectURI: "com.demoapp:/oauthredirect",
                thirdPartyId: "apple",
                code: authCode,
                clientId: "4398792-io.supertokens.example"
            },
            {
                headers: {
                    rid: "thirdpartyemailpassword"
                }
            }
        );

Can you try that?

Still the same

No you need to use the key configuration for your app from the screenshot you sent

Ah my bad, sorry

Yep

Still got the same result

Are you using express for your backend?

Yeah

In the default error handler can you print the full error

Is it the error handler that comes with Supertokens?

No I meant the part that handles errors for your server

app.use((err, req, res, next) => {...})

Looks similar to this

Ok, can you try using your bundle identifier as the client id for both the frontend and the backend and print the full error again on your server

Apple({ isDefault: true, clientId: "BG8TG3D6YB.com.killiansmith.runin", clientSecret: { keyId: process.env.APPLE_KEY_ID!, privateKey: process.env.APPLE_PRIVATE_KEY!, teamId: process.env.APPLE_TEAM_ID!, }, }),

Whats the bundle identifier for the iOS version of your app? (Youll have to check this inside Xcode)

It's an expo application, so It is set to com.killiansmith.runin

Right so use

com.killiansmith.runin

as the client id for the backend and frontend and print the full error on the server

data: { error: 'invalid_grant', error_description: 'client_id mismatch. The code was not issued to com.killiansmith.runin.' }

No thats alright

"ios": { "supportsTablet": true, "bundleIdentifier": "com.killiansmith.runin" },

Are you running on a simulator by chance?

Yes...

Is it possible for you to run on a device?

No I don't own an iPhone, I think I can build the app and run it though

So Apple is known to give invalid codes and tokens on simulators, which breaks the flow when SuperTokens uses the code to fetch user information. If you can test on a device or build for Testflight and then check on someone elses device we can rule that out

Oh wow I didn't know that, that sucks :(

Yep, thanks Apple indeed. But yeah actually trying it out would tell us more, if you can build for Testflight I could join the testers and try it out for you if that makes it easier

Yeah, thank you! I'll try and build the app, and I'll let you know

Oh awesome, glad you could make it work! Strange that expo does not honor the bundle id you set in your config in dev mode but yeah thats useful to know for future issues too