v2.1.2

🚀 Release Notes - v2.1.2

✨ What's New

📱 Android Browser Fallback Improvements

We've enhanced the Android implementation to provide better browser selection logic:

• 🌟 Chrome Priority: The library now prioritizes Chrome Custom Tabs when Chrome is installed on the device, ensuring the best user experience with familiar Chrome features.
• 🔄 Graceful Fallback: On devices without Chrome (such as some Samsung devices), the library falls back to opening URLs in the device's default web browser using the standard Intent.ACTION_VIEW mechanism.
• 🎯 No More Unwanted Custom Tabs: Previously, the library might have used other browsers' Custom Tabs implementations (e.g., Samsung Internet). Now it only uses Chrome Custom Tabs when available, otherwise defaults to the system browser.

This change addresses compatibility issues on devices where Chrome is not the default or not installed, while maintaining optimal performance when Chrome is available.

📚 Documentation Updates

• Added a new "Android Browser Fallback" section to the README.md with details about the browser selection behavior.
• Improved package.json keywords for better discoverability on npm, including terms like "in-app-browser", "custom-tabs", "oauth", "authentication", and platform-specific keywords.

🔧 Technical Changes

• Modified CustomTabsPackageHelper.kt to prefer Chrome package when available.
• Updated HybridInappbrowserNitro.kt to only attempt Custom Tabs launch when Chrome is the selected provider.
• Enhanced README.md with collapsible details section for Android behavior.
• Expanded package.json keywords array from 2 to 15 relevant terms.

✅ Compatibility

• No breaking changes to the API.
• Maintains backward compatibility with existing code.
• Works across all supported Android versions (API 23+).

🛠️ Migration

No migration steps required. The changes are internal improvements that enhance behavior without changing the public API.