React Native Android应用从Play Store安装后无法获取Branch推荐数据

I’ve run into a nearly identical issue with Branch.io attribution on React Native Android apps before—everything works great in test cases but breaks when users install via the Play Store. Let’s break down the most likely fixes and checks based on your scenario:

Core Problem Recap #

Our cross-platform React Native app uses Branch.io for install tracking and deep linking. iOS works flawlessly across all scenarios, and Android passes all Branch’s official test cases (like pre-installed app + link clicks, etc.). However, when users are directed to the Play Store via a Branch link to download the app, no referral data is retrieved post-install. We’ve identified 3 specific failing scenarios here.

Key Troubleshooting Steps #

1. Validate Android App Links Configuration #

Branch relies on App Links to retroactively attribute installs from Play Store links. Double-check these details:

• Confirm your Android package name is correctly registered in the Branch dashboard, and your assetlinks.json file is hosted at https://your-domain.com/.well-known/assetlinks.json (Branch generates this for you—just make sure it’s uploaded properly).
• In your AndroidManifest.xml, the target Activity must have an intent-filter with your Branch scheme, App Links host, and the android:autoVerify="true" flag. Example snippet:

  <intent-filter android:autoVerify="true">
      <action android:name="android.intent.action.VIEW" />
      <category android:name="android.intent.category.DEFAULT" />
      <category android:name="android.intent.category.BROWSABLE" />
      <data android:scheme="https" android:host="your-branch-subdomain.app.link" />
  </intent-filter>
  

• Test App Links functionality with adb: Run adb shell am start -a android.intent.action.VIEW -d "https://your-branch-link"—it should open your app directly, not a browser.

2. Fix Branch Initialization & Attribution Fetch Order #

In React Native, timing is critical for Branch data retrieval:

• Initialize Branch as early as possible (root component’s useEffect or componentDidMount) before trying to fetch referral params.
• Use getFirstReferringParams() for post-install attribution (this captures the first install source), not getLatestReferringParams() (which is for recent link clicks after the app is installed).
• Add logging around these calls to confirm when data is being fetched—example:

  import branch from 'react-native-branch';
  
  useEffect(() => {
    branch.initSession().then((params) => {
      console.log('Branch init params:', params);
      // Use getFirstReferringParams here for install attribution
      branch.getFirstReferringParams().then((installParams) => {
        console.log('Install referral data:', installParams);
      });
    }).catch((err) => console.error('Branch init error:', err));
  }, []);
  

3. Verify Play Store Integration in Branch Dashboard #

Branch needs to sync with Google Play to capture install referrals:

• In your Branch dashboard’s Android app settings, ensure you’ve entered the correct Google Play Store ID and enabled the "Google Play Install Referrer" option.
• Confirm your app includes the Google Play Install Referrer Library (the official React Native Branch SDK should bundle this, but you can double-check your build.gradle dependencies).
• Use Branch’s test links to simulate the flow: Generate a test link, open it in a browser to trigger the Play Store redirect, install the app, and check Branch’s Liveview dashboard for attribution data.

4. Rule Out Third-Party Interference #

Some tools can block or modify install referrer data:

• If you’re using other analytics/attribution SDKs (like Firebase), ensure they’re not conflicting with Branch’s referrer capture.
• Test on a clean device (no security apps, alternative app stores) to eliminate external interference.
• Check system logs for referrer data with adb logcat -s InstallReferrerReceiver—this will show if the Play Store is sending the correct referrer to your app.

5. Deep Dive Into Your 3 Specific Scenarios #

For each failing case, gather these details to narrow down the issue:

• Exact Branch link parameters used in each scenario
• Device model, Android version, and Play Store app version
• Check Branch’s Link Analytics to see if installs are being tracked at all (even if referral data is missing)
• Add granular logging in your app to capture Branch init status, param fetch results, and any errors

内容的提问来源于stack exchange，提问作者Philberg