s-alad / toofake

View friends BeReals without posting or them knowing. Post custom BeReal's whenever. Add custom realmojis
https://toofake.lol/
MIT License
158 stars 35 forks source link

Getting 'APP_NOT_VERIFIED' when trying to sign in via phone number #8

Closed retoheusser closed 1 year ago

retoheusser commented 1 year ago

GET /sendotp/{phone number} HTTP/1.1 logs the following error that it is getting from the remote server:

{
    "error": {
        "code": 400,
        "message": "APP_NOT_VERIFIED",
        "errors": [
            {
                "message": "APP_NOT_VERIFIED",
                "domain": "global",
                "reason": "invalid"
            }
        ]
    }
}

Do you know how to fix this? Is any environment variable or token missing that's required for the login?

s-alad commented 1 year ago

what phone num# extension are you using?

retoheusser commented 1 year ago

+41 (Switzerland)

s-alad commented 1 year ago

Might be some header issues, I pushed a new version could you try that? Does https://toofake.vercel.app/ work with your swiss number?

retoheusser commented 1 year ago

I tried, but it doesn't work so far. Can you see something in the logs on vercel?

s-alad commented 1 year ago

I don't have any logs for privacy reasons. Is your phone number being inputted like this? image I just tried a virtual swiss sms and it seemed to be working fine so I'm not really sure what the issue might be.

You can try this endpoint in your url bar: https://toofake.up.railway.app/sendotp/+41{your-number} and see what response you get, it might be different

retoheusser commented 1 year ago

Yes the input was correct. I tried with the endpoint you provided, and this seems to work, it returned a token as session info.

s-alad commented 1 year ago

I have no idea what's going on then tbh, the endpoint should be the exact same, maybe its how the phone number is being passed from my client to backend? I'll take another look at it soon

retoheusser commented 1 year ago

Hey, I don't think it's an issue with your client anymore as now I get a session info as expected instead of APP_NOT_VERIFIED. It behaves the same as the original app for that part. I'll close this issue then 👍🏽

s-alad commented 1 year ago

did it fix itself somehow? are you able to view things as normal?

retoheusser commented 1 year ago

After I opened the issue, you committed a few things which I pulled and then it was working normally...