#databus_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1389952062409801779
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there ๐ the return URL field should accept custom schemas like that, can you share the ID of the request you made that returned an error about this?
the image is enough or you need the id?
this is another request id that has the same problem
pi_3ReXqwAomaUaBnvu0yOVsv6w
I don't think that's a valid URL, that looks like it's just the schema. (it'd be like passing us https://, with no path after the protocol for us to send things to)
we are using an expo library to get the uri scheme, that is what it return and it should point to the home of the application
Does the request stop failing if you put anything after the schema?
we didn't try it, we got this problem in production
Can you try it?
If you hit this problem in livemode, I'd expect you to have encountered it in your test flow as well. Is that not the case? If so, can you share the ID of the request you made in testmode that behaved differently than livemode?
So it looks like it works if you complete the URL and provide a path following the schema?
I don't think it is, where does it point to? It doesn't have any path.
we doesn't have path, we are using a navigator to manage the navigation through the pages
we are developing with expo not android studio
so i'm not sure on how the navigation should work
https://docs.expo.dev/versions/latest/sdk/linking/#linkingcreateurlpath-namedparameters this is the method that we are using