How to force Google to refetch .well-known/assetlinks.json in order to fix my Android App Link implementation

Troubleshooting Android App Links: Forcing Google to Refetch assetlinks.json

Android App Links are essential for a seamless user experience, enabling direct access to your app from web links. However, sometimes, issues arise during implementation, and you might need to force Google to refetch the assetlinks.json file for proper recognition. This article guides you through troubleshooting and forcing a refresh.

Understanding Assetlinks.json

The assetlinks.json file acts as a bridge between your website and your Android app. It contains information about which web pages are associated with your app. Google uses this file to determine if an intent can be handled by your app.

Common Reasons for Refetching

1. Newly Added Links

If you’ve added new web pages to your site that should open your app, you need to update the assetlinks.json file and force a refetch.

2. Changes to Domain or App Package Name

Any modifications to your domain name or the package name of your Android app will require refetching the file.

3. Configuration Errors

If you’ve made mistakes in the assetlinks.json file, it might not be correctly parsed by Google. Refetching will help resolve these issues.

Methods for Forcing Refetch

There are a few ways to trigger Google to re-evaluate your assetlinks.json file.

1. Clearing App Data (Android)

• Go to your device’s settings.
• Find “Apps & notifications” or “Installed apps.”
• Locate your app and tap on it.
• Tap on “Storage & cache.”
• Select “Clear Cache” and “Clear Data.”

This removes temporary data related to the app and encourages a fresh fetch of assetlinks.json.

2. Using the Google URL Shortener API

The Google URL Shortener API allows you to programmatically control the creation and shortening of URLs. By using this API to generate a new short URL pointing to your assetlinks.json file, you can prompt Google to fetch the latest version.

Example:

curl -X POST -d 'longUrl=https://example.com/.well-known/assetlinks.json' \
  https://www.googleapis.com/urlshortener/v1/shorten

Output:

{
  "id": "http://goo.gl/f1Q2",
  "longUrl": "https://example.com/.well-known/assetlinks.json"
}

By accessing the generated short URL, Google will retrieve the latest version of assetlinks.json.

3. Manual Testing Through the ‘android-app’ Meta Tag

To test the validity of your assetlinks.json file, add a meta tag with the android-app attribute in your HTML.

This tells Google which app should handle links from this page. By testing links to pages with this meta tag, you can see if Google is correctly identifying your app for these links.

Best Practices for Assetlinks.json

• Place assetlinks.json at the root of your website under /.well-known.
• Ensure proper syntax and JSON formatting.
• Use clear and concise language for descriptions.
• Test thoroughly and monitor for issues.

Table for Comparison

Conclusion

Successfully implementing Android App Links involves configuring assetlinks.json correctly. When issues arise, these methods will help you force Google to refetch the file and ensure accurate app linking for a smooth user experience.