Linking.getInitialURL() for android #25675

sajaddp · 2019-07-16T13:34:06Z

Hi,
On Android Linking.getInitialURL() has a problem and not return anything.
More precisely, none of the following logs are executed.

  Linking.getInitialURL().then((url) => {
      console.log('Initial url is: ' + url);
  }).catch(err => console.error('An error occurred', err));

but when i change https://github.com/facebook/react-native/blob/master/Libraries/Linking/Linking.js#L86-L92
to:

  getInitialURL(): Promise<?string> {
    return NativeLinking.getInitialURL();
  }

the problem was fixed.

React Native version:

System:
    OS: Linux 4.18 Ubuntu 18.04.2 LTS (Bionic Beaver)
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Memory: 582.26 MB / 15.50 GB
    Shell: 4.4.20 - /bin/bash
  Binaries:
    Node: 10.16.0 - /usr/bin/node
    Yarn: 1.17.3 - /usr/bin/yarn
    npm: 6.9.0 - /usr/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    Android SDK:
      API Levels: 28
      Build Tools: 28.0.3, 29.0.0, 29.0.1
      System Images: android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom
      Android NDK: 20.0.5594570
  npmPackages:
    react: 16.8.6 => 16.8.6 
    react-native: 0.60.3 => 0.60.3 
  npmGlobalPackages:
    react-native-cli: 2.0.1

The text was updated successfully, but these errors were encountered:

tgensol · 2019-09-06T09:13:24Z

I can confirm that on Android, if the app is closed, InteractionManager.runAfterInteractions, will not work and then the getInitialURL will not return anything.

But if the app was opened, everything works just fine.

I removed the InteractionManager.runAfterInteractions and the deep linking on Android, when the app is closed, works again

Thanks @sajaddp

i7soft · 2019-09-26T13:12:30Z

I fixed by that:

var NativeLinking=require("./node_modules/react-native/Libraries/Linking/NativeLinking").default;
NativeLinking.getInitialURL().then((url) => {
      console.log('Initial url is: ' + url);
  }).catch(err => console.error('An error occurred', err));

shubham234 · 2019-11-16T14:47:10Z

I'm also facing this issue on RN v0.59.8. I'm trying to use aws-amplify library and they make use of Linking.getInitialUrl() to listen to the Deeplink URL but it is always returning null. Can anyone suggest some solutions that I can try?

joaocac · 2020-01-28T09:07:14Z

Same here iOS is working great but Android fails.

System:
    OS: macOS 10.15.2
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Memory: 68.70 MB / 16.00 GB
Packages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.2 => 0.61.2
    react-native-cli: 2.0.1

mileszs · 2020-01-28T20:07:40Z

We are seeing what we think is the same issue—works great on iOS, fails on Android cold starts. In particular, it fails on Android 10. It works on an old Android 7 phone I have.

Stephen2 · 2020-02-19T00:06:36Z

Any update on this? Or workaround?

Stephen2 · 2020-02-19T16:14:32Z

Interestingly, getInitialUrl works on Google Pixel XL2 but doesn't work on Samsung S9 - both running Android 10.

I even changed code to:
import NativeLinking from "react-native/Libraries/Linking/NativeLinking";
NativeLinking.getInitialURL().then(handleDeepLinking);
(^^ code is cut down, I actually went as far as to put url into state and display in a <Text> for debug build, but nothing)

But to no avail... Samsung S9 refuses to call the handleDeepLinking function from cold start :( Warm start is fine, and anyway warm start is handled by Linking.addEventListener("url", ev => {

Stephen2 · 2020-02-19T16:15:17Z

"react": "16.9.0",
"react-native": "0.61.4",
"expo": "^36.0.0",

Stephen2 · 2020-02-24T20:28:19Z

UPDATE:

forking react-native and reverting [Android] Make Linking.getInitialURL works properly even if current activity is not initialized #24748 did NOT solve the issue
I downgraded Expo SDK from 36 to 35, which moved react-native from 0.61.4 back to 0.59.8 which did solve the issue

And please note the differing behaviour on different Android devices during my testing. This was a consistent failure on Samsung, but consistently fine on Google Pixel

I will attempt to do a git log --follow on a few files between these 2 react-native versions, to get more info, but at this point I don't know which files/folders are most likely culprits.

aurasphere · 2020-02-25T13:38:22Z

I can confirm that I have this issue since I've updated from 0.59.* to 0.61.*

phillipkey · 2020-03-06T19:13:10Z

Is there any update on this issue? I'm experiencing the same. Not being able to utilize deep linking is a huge miss right now.

bsonmez · 2020-03-17T11:33:22Z

Is there any update? The bug still continues

openwell · 2020-03-17T17:53:17Z

Finally am not dumb.... Is there any update? The bug still continues

ryzhak · 2020-03-20T13:27:58Z

The same issue. Linking.getInitialURL works fine on ios, but on android(emulator SDK 28) this method seems not even to be called.

"react-native": "0.61.5",
"react-native-navigation": "^4.5.3",

danieltrizzuto · 2020-04-01T20:02:47Z

Same here on 0.61.5

xanderdeseyn · 2020-04-05T10:07:42Z

Any progress on this? Seems mind boggling to me that deeplinking is just completely broken in RN for Android?

norbertschuler · 2020-04-05T12:03:01Z

Any progress on this? Seems mind boggling to me that deeplinking is just completely broken in RN for Android?

It’s not completely broken for me. It works for an already started app, but not for a newly started one.

xanderdeseyn · 2020-04-07T17:36:48Z

Any progress on this? Seems mind boggling to me that deeplinking is just completely broken in RN for Android?

It’s not completely broken for me. It works for an already started app, but not for a newly started one.

Well I'd argue that is almost completely broken then. Deeplinking is usually used when the app is not open.

rsmelo92 · 2020-04-10T21:48:07Z

The culprit seems to be this line here

react-native/Libraries/Linking/Linking.js

Line 88 in c0d8c1d

? InteractionManager.runAfterInteractions().then(() =>

InteractionManager.runAfterInteractions takes too long and Linking.getInitialURL never resolves the desired effect!

After removing it it worked 100% of the times, so @Stephen2 workaround actually fixes it by the time being...

import NativeLinking from 'react-native/Libraries/Linking/NativeLinking';
NativeLinking.getInitialURL().then(url => {
      handleDeepLink({ url });
 });

Stephen2 · 2020-04-10T22:00:36Z

import NativeLinking from 'react-native/Libraries/Linking/NativeLinking';
NativeLinking.getInitialURL().then(url => {
      handleDeepLink({ url });
 });

I've tried that earlier

But to no avail... Samsung S9 refuses to call the handleDeepLinking function from cold start

lnwanghao · 2022-02-23T04:49:31Z

It's seems still a bug when app is from background to foreground Linking.getInitialURL return null

Balthazar33 · 2022-04-13T12:38:30Z

In our case, it turned out that our intentFilters were not configured properly. Everything works fine on Android without any workarounds.

Hi @footniko
Could you please mention what was missing?

Balthazar33 · 2022-04-13T13:48:16Z

I ended up using this workaround:

In App.js:

import NfcManager from 'react-native-nfc-manager';

useEffect(() => {
    getUrl();
  }, []);
  
async function getUrl() {
    let event = await NfcManager.getLaunchTagEvent();
    console.log('Event', event);
    //Outputs {"id": "A1B2C3D4", "techTypes": ["android.nfc.tech.IsoDep", "android.nfc.tech.NfcA"]}
  }

My AndroidManifest.xml looks like this:

<uses-permission android:name="android.permission.NFC" />

<application>
  <activity>
       <intent-filter>
          <action android:name="android.nfc.action.TAG_DISCOVERED" />
          <action android:name="android.nfc.action.NDEF_DISCOVERED" />
          <category android:name="android.intent.category.DEFAULT" />
        </intent-filter>
    </activity>
 </application>

RN 0.68.0

kivohin · 2022-04-14T02:02:30Z

In our case, it turned out that our intentFilters were not configured properly. Everything works fine on Android without any workarounds.

Hi @footniko Could you please mention what was missing?

To expand on @footniko answer, we are using Expo SDK v44 (React Native v0.64).
The reason Linking.getInitialURL() was always returning null on Android was because we never configured the intentFilters for Android.

In order to do so when using Expo you need to follow the instructions here:
https://docs.expo.dev/guides/linking/#deep-links-on-android
https://docs.expo.dev/versions/latest/config/app/#intentfilters

Keep in mind, in Expo when you change the app.json or app.config.ts files you need to do a full app store release in order for the changes to apply. You can not do an over-the-air update.

If you are not using Expo then you will probably need to apply the same Intent Filter changes but in the AndroidManifest.xml file.

soulfresh · 2022-10-13T20:45:42Z

import { Linking, Platform } from 'react-native'
import NativeIntentAndroid from 'react-native/Libraries/Linking/NativeIntentAndroid'

const NativeLinking = Platform.OS === 'android' ? NativeIntentAndroid : Linking

NativeLinking.getInitialURL().then(url => console.log(url))

I was struggling with this issue recently as well and found two things. 1) The above resolved the issue on Android for me. 2) The root cause of my issue actually turned out to be a custom animation using React Native Animation running at the same time that Linking was trying to get the initial URL. I haven't tracked down exactly what it is about the animation that was preventing InteractionManager.runAfterInteractions from firing on Android but preventing my animation from running resolved the Linking error without having to resort to NativeIntentAndroid.

Hope that helps someone.

Summary: This was originally added in D15258046 (facebook@c802d0b) but seems to be the wrong solution to the problem from my perspective. InteractionManager does not provide timing information on the activity being available, but ReactContext's LifecycleEventListener does. This should also address some of the issues raised in facebook#25675 Changelog: [Android][Fixed] Linking.getInitialUrl should not wait for InteractionManager Differential Revision: D41157646 fbshipit-source-id: 486088e2948c0c0c83bbfbd25036e1f34017429f

Summary: Pull Request resolved: facebook#35289 This was originally added in D15258046 (facebook@c802d0b) but seems to be the wrong solution to the problem from my perspective. InteractionManager does not provide timing information on the activity being available, but ReactContext's LifecycleEventListener does. This should also address some of the issues raised in facebook#25675 Changelog: [Android][Fixed] Linking.getInitialUrl should not wait for InteractionManager Differential Revision: D41157646 fbshipit-source-id: 610ee440c38cb6e5b7e0b8d808e0e2e73599404c

Summary: Pull Request resolved: #35289 This was originally added in D15258046 (c802d0b) but seems to be the wrong solution to the problem from my perspective. InteractionManager does not provide timing information on the activity being available, but ReactContext's LifecycleEventListener does. This should also address some of the issues raised in #25675 Changelog: [Android][Fixed] Linking.getInitialUrl should not wait for InteractionManager Reviewed By: mdvacca Differential Revision: D41157646 fbshipit-source-id: 6e23969212570204a7e076b6d4d9db004412da09

vincent-odukwe · 2023-03-16T17:25:02Z

In our case, it turned out that our intentFilters were not configured properly. Everything works fine on Android without any workarounds.

what did you fix in your intentFilters @footniko ?

footniko · 2023-03-23T08:42:07Z

In our case, it turned out that our intentFilters were not configured properly. Everything works fine on Android without any workarounds.

what did you fix in your intentFilters @footniko ?

Check this reply: #25675 (comment)

rveruna · 2023-04-25T10:06:18Z

Still an issue in 0.68.5.
I went aroud it by using
import NativeIntentAndroid from 'react-native/Libraries/Linking/NativeIntentAndroid';
NativeIntentAndroid.getInitialURL().then(handleUrl);

Summary: Pull Request resolved: facebook#35289 This was originally added in D15258046 (facebook@c802d0b) but seems to be the wrong solution to the problem from my perspective. InteractionManager does not provide timing information on the activity being available, but ReactContext's LifecycleEventListener does. This should also address some of the issues raised in facebook#25675 Changelog: [Android][Fixed] Linking.getInitialUrl should not wait for InteractionManager Reviewed By: mdvacca Differential Revision: D41157646 fbshipit-source-id: 6e23969212570204a7e076b6d4d9db004412da09

github-actions · 2023-10-23T05:01:21Z

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

GuillaumeHemmen · 2023-10-23T05:04:33Z

This issue is still valid IMO; please remove the stale label.

MaryKilduff68 · 2024-01-24T15:04:55Z

Has there been any update on this issue?

fabOnReact · 2024-01-31T03:36:16Z

could you provide a minimum reproducible example?
Can you reproduce this issue using an existing minimum reproducible example (like this one #25675 (comment)) and adding steps explained by #25675 (comment)?

It is documented also in the react-native documentation https://reactnative.dev/docs/next/linking#getinitialurl

To support deep linking on Android, refer https://developer.android.com/training/app-indexing/deep-linking.html#handling-intents
getInitialURL may return null while debugging is enabled. Disable the debugger to ensure it gets passed.

tmitchel2 · 2024-02-23T10:43:39Z

I've just started to get this issue after upgrading to 0.73, it is adding approximately 10s onto my app startup time waiting to resolve the promise.

It looks like in 0.73 the code has been moved to native code so the above workarounds will now no longer work.

Also for me I think the reason I get this is due to the fact im calling Linking.getInitialUrl as early as possible in my app start, even before a screen has been rendered. I don't really want to change this because the initial url can actually determine alot about how my app starts up in testing scenarios.

I can only think that it should be optional to wait for an activity? (im not up on android app lifecycles though)

stephenkopylov · 2024-03-15T15:58:38Z

Facing this issue sometimes while trying to get initial url as soon as possible on the startup

Seems like something relates to the this topic

Error
Cannot await activity from more than one call to getInitialURL

    IntentModule:84 com.facebook.react.modules.intent.IntentModule.waitForActivityAndGetInitialURL
    IntentModule:59 com.facebook.react.modules.intent.IntentModule.getInitialURL
    Method.java:-2 java.lang.reflect.Method.invoke
    JavaMethodWrapper:372 com.facebook.react.bridge.JavaMethodWrapper.invoke
    JavaModuleWrapper:149 com.facebook.react.bridge.JavaModuleWrapper.invoke
    SourceFile:-2 com.facebook.jni.NativeRunnable.run
    Handler.java:743 android.os.Handler.handleCallback
    Handler.java:95 android.os.Handler.dispatchMessage
    MessageQueueThreadHandler:27 com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage
    Looper.java:150 android.os.Looper.loop
    MessageQueueThreadImpl:234 com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run
    Thread.java:833 java.lang.Thread.run
    node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:105:59 promiseMethodWrapper
    node_modules/react-native/Libraries/Linking/Linking.js:98:53 getInitialURL
    node_modules/@react-navigation/native/src/useLinking.native.tsx:31:29 anonymous
    node_modules/@react-navigation/native/src/useLinking.native.tsx:141:42 anonymous
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:3771:68 mountState
    node_modules/react/cjs/react.production.min.js:25:401 useState
    node_modules/@react-navigation/native/src/useThenable.tsx:4:34 useThenable
    node_modules/@react-navigation/native/src/NavigationContainer.tsx:103:48 NavigationContainerInner
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:3525:21 renderWithHooks
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:4316:29 updateForwardRef
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:7929:24 beginWork$1
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:7304:24 performUnitOfWork
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:7297:53 workLoopSync
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:7279:18 renderRootSync
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:6975:33 performSyncWorkOnRoot
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:2145:30 flushSyncCallbacks
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:8462:57 batchedUpdatesImpl
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:1106:29 batchedUpdates
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:1137:16 _receiveRootNodeIDEvent
    node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js:1178:27 receiveEvent
    (native) apply
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:433:33 __callFunction
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:113:25 anonymous
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:368:10 __guard
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:112:16 callFunctionReturnFlushedQueue

TomasSestak · 2024-05-03T13:07:46Z

still valid

pwltr · 2024-05-03T13:15:30Z

@TomasSestak I did extensive testing on this yesterday and didn't find an issue with getInitialUrl on Android. In my case it was a mistake on my part dealing with NFC. I suggest trying to create a minimal reproducible example to figure out if the bug is with your application.

omerts · 2024-05-09T12:36:48Z

Just got it from crashyltics with latest RN.
issue_022302da0d55dfb152b0c7d7d51a24a7_crash_session_663CA92000DE0001293FA011CE78595B_DNE_1_v2_stacktrace.txt

BlackMonday-ai · 2024-05-26T02:35:45Z

I am also facing this problem
"expo": "~51.0.8",
"react-native": "0.74.1",

other
"dependencies": {
"@expo/metro-runtime": "~3.2.1",
"@expo/vector-icons": "^14.0.0",
"@react-native-community/masked-view": "^0.1.11",
"@react-navigation/bottom-tabs": "^6.5.20",
"@react-navigation/drawer": "^6.6.15",
"@react-navigation/material-top-tabs": "^6.6.13",
"@react-navigation/native": "^6.1.17",
"@react-navigation/native-stack": "^6.9.26",
"expo": "~51.0.8",
"expo-application": "~5.9.1",
"expo-auth-session": "~5.5.2",
"expo-constants": "~16.0.1",
"expo-crypto": "~13.0.2",
"expo-dev-client": "~4.0.14",
"expo-device": "~6.0.2",
"expo-font": "~12.0.5",
"expo-linear-gradient": "~13.0.2",
"expo-linking": "~6.3.1",
"expo-notifications": "~0.28.3",
"expo-secure-store": "~13.0.1",
"expo-status-bar": "~1.12.1",
"expo-web-browser": "~13.0.3",
"lottie-react-native": "6.7.0",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-native": "0.74.1",
"react-native-gesture-handler": "~2.16.1",
"react-native-linear-gradient": "^2.8.3",
"react-native-modal": "^13.0.1",
"react-native-reanimated": "~3.10.1",
"react-native-safe-area-context": "4.10.1",
"react-native-screens": "3.31.1",
"react-native-swipe-up-down": "^1.2.0",
"react-native-tab-view": "^3.5.2",
"react-native-vector-icons": "^10.0.3",
"react-native-web": "~0.19.6",
"react-redux": "^9.1.0",
"redux": "^5.0.1"
},

import NativeIntentAndroid from 'react-native/Libraries/Linking/NativeIntentAndroid'
const NativeLinking = NativeIntentAndroid;
const getUrl = await NativeLinking.getInitialURL();
still got null

BlackMonday-ai · 2024-06-01T14:41:24Z

any work around?

sajaddp added the Bug label Jul 16, 2019

react-native-bot added API: Linking Platform: Android Android applications. Platform: Linux Building on Linux. labels Jul 16, 2019

shubham234 mentioned this issue Nov 16, 2019

Linking.getInitialUrl always returning null in Android #27242

Closed

This was referenced Feb 14, 2020

Linking.getInitialUrl never returns #26947

Closed

[Android] Make Linking.getInitialURL works properly even if current activity is not initialized #24748

Closed

Tapokj mentioned this issue Feb 27, 2020

Deep link not working in testflight if page is active. react-navigation/react-navigation#7679

Closed

satya164 mentioned this issue Mar 17, 2020

useLinking issue on Android react-navigation/react-navigation#6575

Closed

norbertschuler mentioned this issue Mar 24, 2020

Deep Link to tree counter opens App but not tree counter (android only) Plant-for-the-Planet-org/treecounter-app#2021

Closed

javache mentioned this issue Nov 9, 2022

Do not use InteractionManager to wait for Activity #35289

Closed

github-actions bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Oct 23, 2023

github-actions bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Oct 23, 2023

cortinico added the Never gets stale Prevent those issues and PRs from getting stale label Oct 24, 2023

fortesdev mentioned this issue Apr 18, 2024

Deep Link Handling in Notifications infobip/mobile-messaging-react-native-plugin#71

Open

nick42d mentioned this issue Apr 29, 2024

Opening app from headless notification doesn't open tracker nick42d/LawnTrackerApp#14

Open

sajaddp closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2024

Linking.getInitialURL() for android #25675

Linking.getInitialURL() for android #25675

Comments

sajaddp commented Jul 16, 2019

tgensol commented Sep 6, 2019

i7soft commented Sep 26, 2019

shubham234 commented Nov 16, 2019

joaocac commented Jan 28, 2020 • edited Loading

mileszs commented Jan 28, 2020

Stephen2 commented Feb 19, 2020

Stephen2 commented Feb 19, 2020 • edited Loading

Stephen2 commented Feb 19, 2020

Stephen2 commented Feb 24, 2020

aurasphere commented Feb 25, 2020

phillipkey commented Mar 6, 2020

bsonmez commented Mar 17, 2020 • edited Loading

openwell commented Mar 17, 2020

ryzhak commented Mar 20, 2020

danieltrizzuto commented Apr 1, 2020

xanderdeseyn commented Apr 5, 2020

norbertschuler commented Apr 5, 2020

xanderdeseyn commented Apr 7, 2020

rsmelo92 commented Apr 10, 2020

Stephen2 commented Apr 10, 2020

lnwanghao commented Feb 23, 2022

Balthazar33 commented Apr 13, 2022

Balthazar33 commented Apr 13, 2022

kivohin commented Apr 14, 2022

soulfresh commented Oct 13, 2022

vincent-odukwe commented Mar 16, 2023

footniko commented Mar 23, 2023

rveruna commented Apr 25, 2023

github-actions bot commented Oct 23, 2023

GuillaumeHemmen commented Oct 23, 2023

MaryKilduff68 commented Jan 24, 2024

fabOnReact commented Jan 31, 2024 • edited Loading

tmitchel2 commented Feb 23, 2024

stephenkopylov commented Mar 15, 2024

TomasSestak commented May 3, 2024

pwltr commented May 3, 2024

omerts commented May 9, 2024

BlackMonday-ai commented May 26, 2024 • edited Loading

BlackMonday-ai commented Jun 1, 2024

joaocac commented Jan 28, 2020 •

edited

Loading

Stephen2 commented Feb 19, 2020 •

edited

Loading

bsonmez commented Mar 17, 2020 •

edited

Loading

fabOnReact commented Jan 31, 2024 •

edited

Loading

BlackMonday-ai commented May 26, 2024 •

edited

Loading