Has anybody seen this error? API input error: Plea...
# support-questions-legacyd
davido_k
02/25/2023, 10:35 PMHas anybody seen this error? API input error: Please make sure to pass valid URL query params
2023-02-25T22:28:00.818Z com.supertokens {t: "2023-02-25T22:28:00.818Z", message: "errorHandler: Started", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/supertokens.js:321:26" sdkVer: "13.0.2"}
2023-02-25T22:28:00.818Z com.supertokens {t: "2023-02-25T22:28:00.818Z", message: "errorHandler: Error is from SuperTokens recipe. Message: API input error: Please make sure to pass valid URL query params", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/supertokens.js:323:30" sdkVer: "13.0.2"}
2023-02-25T22:28:00.818Z com.supertokens {t: "2023-02-25T22:28:00.818Z", message: "errorHandler: Sending 400 status code response", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/supertokens.js:325:34" sdkVer: "13.0.2"}
2023-02-25T22:28:00.819Z com.supertokens {t: "2023-02-25T22:28:00.818Z", message: "Sending response to client with status code: 400", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/utils.js:133:14" sdkVer: "13.0.2"}
I'm getting it when trying to implement Sign In with Apple. I'm POSTing to /api/auth/callback/apple a
statecoder
rp_st
02/26/2023, 5:35 AMare you manually posting to that path or is apple doing it? If you are manually posting, can i see how?
d
davido_k
02/26/2023, 5:35 AMit's being posted by Apple
r
rp_st
02/26/2023, 5:38 AMcan you show your nextjs backend api code which handles this request?
rp_st
02/26/2023, 5:38 AM(the api function that uses supertokens middleware)
rp_st
02/26/2023, 5:38 AMand also the supertokens.init on the backend
d
davido_k
02/26/2023, 5:48 AM Copy code
import { superTokensNextWrapper } from "supertokens-node/nextjs"
import { middleware } from "supertokens-node/framework/express"
import supertokens from "supertokens-node"
import { backendConfig } from "../../../config/backendConfig"
import NextCors from "nextjs-cors"
import { websiteDomain } from "../../../config/appInfo"
supertokens.init(backendConfig())
export default async function superTokens(req, res) {
// NOTE: We need CORS only if we are querying the APIs from a different origin
await NextCors(req, res, {
methods: ["GET", "HEAD", "PUT", "PATCH", "POST", "DELETE"],
origin: websiteDomain,
credentials: true,
allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()]
})
await superTokensNextWrapper(
async (next) => {
// This is needed for production deployments with Vercel
res.setHeader("Cache-Control", "no-cache, no-store, max-age=0, must-revalidate")
await middleware()(req, res, next)
},
req,
res
)
if (!res.writableEnded) {
res.status(404).send("Not found")
}
}r
rp_st
02/26/2023, 5:49 AMcan you remove the
NextCorsres.setHeader("Cache-Control", "no-cache, no-store, max-age=0, must-revalidate")d
davido_k
02/26/2023, 5:57 AMdidn't help. If interested, you can inspect the client-side bits at https://qa.dvcforless.com/auth
davido_k
02/26/2023, 5:57 AMNothing too exciting, though
r
rp_st
02/26/2023, 6:09 AMthis may be a bug in our library. Can you please open an issue about this on our github, and we will check it out in the coming week.
rp_st
02/26/2023, 7:03 AMhey @davido_k so this is indeed a bug in our lib. We will fix it asap. You can follow this issue to know the status: https://github.com/supertokens/supertokens-node/issues/496
d
davido_k
02/26/2023, 2:44 PMthanks!
r
rp_st
02/27/2023, 5:39 PMhey @davido_k we have released a new version of the node SDK with the fix.
d
davido_k
03/05/2023, 4:33 AM@rp_st I finally got back to this but am receiving a new error in the thirdPartySignInUpPOST method.
Copy code
2023-03-05T04:30:32.767Z com.supertokens {t: "2023-03-05T04:30:32.767Z", message: "middleware: Request being handled by recipe. ID is: /signinup", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/supertokens.js:280:30" sdkVer: "13.1.2"}
2023-03-05T04:30:33.633Z com.supertokens {t: "2023-03-05T04:30:33.633Z", message: "errorHandler: Started", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/supertokens.js:323:26" sdkVer: "13.1.2"}
error - Error: SuperTokens core threw an error for a POST request to path: '/recipe/signinup' with status code: 400 and message: Field name 'id' is invalid in JSON input
at Querier.<anonymous> (/Users/dave/Code/node_modules/supertokens-node/lib/build/querier.js:259:31)
at Generator.throw (<anonymous>)
at rejected (/Users/dave/Code/node_modules/supertokens-node/lib/build/querier.js:22:44)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
page: '/api/auth/[[...path]]'
} Copy code
let response = await originalImplementation.thirdPartySignInUpPOST(input)
console.log("POST - Original complete")r
rp_st
03/05/2023, 4:47 AMHave you give Any custom scope?
d
davido_k
03/05/2023, 5:07 AMno custom scope in the backendConfig. I'll double-check the config on the developer portal
r
rp_st
03/05/2023, 5:07 AMcan you try with our dev keys and check if that works?
d
davido_k
03/05/2023, 5:13 AMhmm, that does work
r
rp_st
03/05/2023, 5:13 AMhmmm
rp_st
03/05/2023, 5:14 AMwhats the configured redirect_uri on the apple dashboard?
d
davido_k
03/05/2023, 5:26 AMthe return url? I have a few /api/auth/callback/apple and /auth/callback/apple are both in there. Or a different setting?
davido_k
03/05/2023, 5:38 AMapple is posting to /api/auth/callback/apple then I send a GET auth/callback/apple?state=f7ac235dxxxxxx...&code=c92 then a post to /api/auth/signinup that returns the 500 from the error above
r
rp_st
03/05/2023, 5:57 AMright. So the redirect uri seems fine
d
davido_k
03/05/2023, 5:57 AMlooks like emailInfo is returning {} here: https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/thirdparty/api/implementation.ts#L144
r
rp_st
03/05/2023, 5:58 AMhmm. @sattvikc can help here sometime tomorrow
d
davido_k
03/05/2023, 5:58 AMthanks
davido_k
03/05/2023, 6:03 AMI found this and it's a pretty good lead of what's going on. Could be a dev artifact or could be a scenario that needs to be covered: https://developer.apple.com/forums/thread/132223
r
rp_st
03/05/2023, 1:56 PMThanks. @sattvikc will have a look tomorrow.
s
sattvikc
03/06/2023, 4:11 AMhi @davido_k could you share what's being posted (payload) to the signinup API by inspecting the network tab in the browser ?
d
davido_k
03/06/2023, 5:40 AM{"code":"c942ed63083c644fba342b6e6e520ab61.0.mwrq.QS54Cccps4yvKDM6ZOASoQ","thirdPartyId":"apple","redirectURI":"https://0ad1-135-134-205-237.ngrok.io/auth/callback/apple"}s
sattvikc
03/06/2023, 5:57 AMmmm okay, give me a min. I'll share a snippet for you to try
sattvikc
03/06/2023, 6:08 AM Copy code
ts
function Apple(config: any) : ThirdParty.TypeProvider {
const appleProvider = ThirdParty.Apple(config);
return {
...appleProvider,
get: function(redirectURI: string | undefined, authCodeResponse: string | undefined, userContext: any) : TypeProviderGetResponse {
console.log("GET: ", redirectURI, authCodeResponse, userContext);
const getResponse = appleProvider.get(redirectURI, authCodeResponse, userContext);
return {
...getResponse,
getProfileInfo: async function(authCodeResponse, userContext) {
console.log("GET PROFILE INFO: ", authCodeResponse);
const result = await getResponse.getProfileInfo(authCodeResponse, userContext);
console.log('PROFILE RESULT', result);
return result;
}
}
}
}
}d
davido_k
03/06/2023, 2:58 PMseems to be working now. My console outputs are returning a valid email object as well. I don't think I changed anything on the Apple developer portal.
`
s
sattvikc
03/08/2023, 5:33 AMmmm okay cool. let me know if you face any issues again
82 Views