Hi There,
I have followed the process outlined in Authenticating With Plex. This works for the most part except when I generate a URL and open it in the browser for authentication.
https://app.plex.tv/auth#?clientID=<clientIdentifier>&code=<pinCode>&context%5Bdevice%5D%5Bproduct%5D=My%20Cool%20Plex%20App&forwardUrl=https%3A%2F%2Fmy-cool-plex-app.com
My issue is with the parameter forwardUrl. As I understand it, if I mention a forwardUrl then once authenticate it should redirect the browser to the given url.
This works perfectly if I mention a URL with the http:// or https:// scheme (i.e. a vanilla webpage on the internet). However, if I give a custom scheme my-app:// it does not work. in fact, it does not even show me the login screen, it just redirects me away to https://plex.tv.
I have this custom scheme, so that it redirects back to the iOS or Android app once authentication has completed.
Are non http:// or https:// url schemes within forwardUrl blocked. It is odd, because I have seen a few apps actually use this (e.g. Infuse 7 on the iOS App Store). They use the intent infuse-oath://plex. And it just works.
My current workaround is to host a static webpage, that then opens up the custom intent url.