Sean,
Thank you! But, these solutions require that the Custom URL is added to the
app at deployment. Not going to work for my client. I was looking to get an
understanding as to why these URLs need to be in the pList. Not sure of the
reasoning behind this... I need to be able to explain
Keith,
Thanks for the assist... In some cases a http call will open the mobile app if
it's installed. For example, https://m.facebook.com will launch the mobile
app. However, now with further testing, I have a new problem. On android, if
the app isn't installed it's not returning "no
Dan,
These will be useful to you:
https://stackoverflow.com/questions/21893447/facebook-sdk-app-not-registered-as-a-url-scheme
https://github.com/facebookarchive/react-native-fbsdk/issues/707
Pi
On Wed, 1 Sept 2021 at 18:38, David Bovill via use-livecode <
use-livecode@lists.runrev.com> wrote:
I don’t know Dan as its been a while since I looked into this - but it sounds
like a typical security thing Apple insists on for the AppStore? They tend
(when compared to Android), to lock that sort of thing down save for a few
standard (internet) url schema.
Schedule a call with me
On 1
Only one thought: the protocols that do work on iOS are general declarations
that are routed to an app/service as the host OS thinks is appropriate. Less
common ones and app-specific ones do have to be registered... in the app that
wants to be able RECEIVE them. So if the FB app doesn’t have
