Issue 11 - layout/design_layout_snackbar_include: Error inflating class android.widget.Button

[LeoJHarris]

*Refactor DefaultUserInterface.cs for Better Error Handling and Code Quality & Prevent Theme-related crashes

The PR essentially says: "I prefer to show a Snackbar, but if your app's theme prevents it, I will gracefully fall back to a Toast and ensure the intended action still takes place, thus maximizing compatibility.

[Copilot]

Pull Request Overview

This PR addresses theme-related crashes in the Android in-app updates library by adding comprehensive error handling and fallback mechanisms to the UI components. The changes focus on resolving the "Error inflating class android.widget.Button" issue mentioned in the title.

• Enhanced error handling in ShowShortToast with null checks and exception catching
• Refactored ShowSnackbar with theme-specific exception handling and toast fallback
• Updated Android package dependencies to newer versions

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
DefaultUserInterface.cs	Added comprehensive error handling, theme-related exception detection, and fallback mechanisms for toast and snackbar operations
Maui.Android.InAppUpdates.csproj	Updated AndroidX and Google Play package versions to newer releases
Maui.Android.InAppUpdates.SampleApp.csproj	Updated Microsoft.Maui.Controls and logging package versions

[LeoJHarris]

@HavenDV github Copilot concerns are probably valid but with the absence of the ability to actually invoke the clickHandler using toast should it auto-trigger or no?

[HavenDV]

I think we use clickHandler only in one place:

        Internal.DefaultUserInterface.ShowSnackbar(
            text: "An update has just been downloaded.",
            actionText: "RESTART",
            clickHandler: static _ => Internal.Handler.AppUpdateManager?.CompleteUpdate());

in this case, if we have issues with UI, it will restart app - so should be ok for users