Custom-URL-scheme icon indicating copy to clipboard operation
Custom-URL-scheme copied to clipboard

FB handle url using application:openURL

Open haveamission opened this issue 5 years ago • 5 comments

I am trying to get the URL via handleOpenURL(), and I am getting the following error message:

2019-08-01 11:51:00.550265-0400 domain[37554:5354467] Got memory pressure notification (non-critical) 2019-08-01 11:51:16.385042-0400 domain[37554:5354467] Got memory pressure notification (non-critical) 2019-08-01 11:51:29.919230-0400 domain[37554:5354787] [BoringSSL] nw_protocol_boringssl_error(1584) [C3.1:2][0x11de390f0] Lower protocol stack error: 53 2019-08-01 11:51:29.919459-0400 domain[37554:5354787] [BoringSSL] nw_protocol_boringssl_error(1584) [C10.1:2][0x11dd440b0] Lower protocol stack error: 53 2019-08-01 11:51:29.924886-0400 domain[37554:5354787] TIC Read Status [3:0x280090fc0]: 1:53 2019-08-01 11:51:29.925341-0400 domain[37554:5354787] TIC Read Status [3:0x280090fc0]: 1:53 2019-08-01 11:51:29.926140-0400 domain[37554:5354787] TIC Read Status [10:0x2800886c0]: 1:53 2019-08-01 11:51:29.926157-0400 domain[37554:5354787] TIC Read Status [10:0x2800886c0]: 1:53 2019-08-01 11:51:30.376922-0400 domain[37554:5354467] FB handle url using application:openURL:options: domain:// 2019-08-01 11:51:30.376987-0400 domain[37554:5354467] FB handle url using application:openURL:options: domain:// 2019-08-01 11:51:30.377026-0400 domain[37554:5354467] FB handle url using application:openURL:options: domain:// 2019-08-01 11:51:30.377063-0400 domain[37554:5354467] FB handle url using application:openURL:options: domain:// 2019-08-01 11:51:30.377101-0400 domain[37554:5354467] FB handle url using application:openURL:options: domain:// 2019-08-01 11:51:30.377136-0400 domain[37554:5354467] FB handle url using application:openURL:options: domain://

It appears to be related to some sort of conflict with FB?

Has anyone seen this?

Domain absolutely has no reference to FB in it at all.

haveamission avatar Aug 01 '19 15:08 haveamission

This answer did the trick for me: https://stackoverflow.com/a/56972533/1167573

c-emil avatar Aug 14 '19 10:08 c-emil

I ultimately switched to Ionic Deeplink, and did a hacky solution on one of their triggers. I’ll look into switching to this though.

haveamission avatar Aug 14 '19 13:08 haveamission

@haveamission Can you share the hacky solution please? Switching to FB 4.2.1 helped in iOS, however breaks Android build...

c-emil avatar Aug 14 '19 13:08 c-emil

if (window.IonicDeeplink) {
  window.IonicDeeplink.onDeepLink(function(data) {
// Do processing here based on Deeplink information
  });

I guess not TOO hacky. But it gives me the information I need.

haveamission avatar Aug 14 '19 13:08 haveamission

I see, interesting, thanks for sharing. Well, luckily, I managed to fix the breaking build. I forgot to update FACEBOOK_ANDROID_SDK_VERSION variable property under the facebook plugin definition. It was still pointing to version 5, whereas the facebook plugin spec was 4.2.1, hence the app was crashing. So I updated it to 4.42.0 which is the latest SDK_VERSION available under major 4.

c-emil avatar Aug 14 '19 13:08 c-emil