Feat/updates andi os26 support

[mCodex]

No description provided.

[Copilot]

Pull Request Overview

This PR represents a comprehensive rewrite and restructuring of the react-native-inappbrowser-nitro library to support iOS 26 and Android 16 features while modernizing the codebase architecture.

• Complete migration from existing architecture to Nitro Modules with enhanced TypeScript bindings
• Addition of iOS 26 features including high-contrast dynamic colors, edge-dismiss control, and UI style overrides
• Implementation of Android 16 capabilities like partial custom tabs, referrer controls, and per-theme color palettes

Reviewed Changes

Copilot reviewed 91 out of 101 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
src/specs/inappbrowser-nitro.nitro.ts	New Nitro module specification with comprehensive type definitions and iOS 26/Android 16 feature support
src/core/InAppBrowser.ts	Redesigned imperative API with URL/options validation and improved error handling
src/utils/options.ts	New utility for sanitizing and normalizing cross-platform browser options
src/utils/url.ts	URL validation and security filtering utilities
src/hooks/useInAppBrowser.ts	Updated React hook with improved async handling and component lifecycle management
ios/HybridInappbrowserNitro.swift	New iOS implementation leveraging Safari View Controller with iOS 26 features
android/src/main/java/com/inappbrowsernitro/HybridInappbrowserNitro.kt	New Android implementation using Custom Tabs with Android 16 enhancements

Files not reviewed (1)

• example/ios/InappbrowserNitroExample.xcworkspace/contents.xcworkspacedata: Language not supported

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Missing JSDoc description for the main script purpose. Consider adding a brief explanation of what this workaround accomplishes for Android builds.

Suggested change

	/**
	/**
	* Workaround script to enable custom package names for Android builds.

[Copilot]

The reflection-based approach to access high contrast settings introduces fragility. Consider adding API level checks or using a more robust detection method to avoid potential crashes on different Android versions.

Suggested change

	internal object DynamicColorResolver {
	fun resolve(context: Context, dynamicColor: DynamicColor?): Int? {
	dynamicColor ?: return null
	val accessibilityManager = context.getSystemService<AccessibilityManager>()
	val isHighContrast = accessibilityManager?.let { manager ->
	runCatching {
	val method = AccessibilityManager::class.java.getMethod("isHighTextContrastEnabled")
	(method.invoke(manager) as? Boolean) == true
	}.getOrDefault(false)
	} == true
	import android.os.Build
	internal object DynamicColorResolver {
	fun resolve(context: Context, dynamicColor: DynamicColor?): Int? {
	dynamicColor ?: return null
	val accessibilityManager = context.getSystemService<AccessibilityManager>()
	val isHighContrast = if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
	accessibilityManager?.isHighTextContrastEnabled == true
	} else {
	false
	}

[Copilot]

Magic number PARTIAL_TAB_RATIO (0.85f) should be documented or made configurable. Consider adding a comment explaining why 85% was chosen as the default partial tab height.

[Copilot]

The hardcoded override for partialCurl transition style should include a comment explaining why fullScreen is required to prevent UIKit crashes, as mentioned in platform differences documentation.

Suggested change

	if transition == .partialcurl {
	if transition == .partialcurl {
	// UIKit requires .fullScreen presentation style when using .partialCurl transition to prevent crashes.
	// See: https://developer.apple.com/documentation/uikit/uiviewcontroller/1621355-modaltransitionstyle