Xamarin.AndroidX.WebKit for .NET9.0 and Android35

Open
#1,270 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, csharp

Research direction

No source files or tests are named. Start by locating the Xamarin.AndroidX.WebKit package build configuration and its existing net8.0-android34.0 and net10.0-android36.0 target entries; done means adding and validating net9.0-android35 support, while the Google Pay WebView behavior remains an additional question.

Written by the indexing model from the issue text.

Description

question update-package-request
Description

Hi,

We have upcoming MAUI project deadlines for implementing Google Pay (hosted WebBrowser) into our MAUI .NET9.0 targetting Android API 35 App which will require us to use AndroidX.WebKit (so we can set appropriate options in UIWebView as per article at https://developers.google.com/pay/api/android/guides/recipes/using-android-webview#enable-payment-request-api ) .

The NuGet REPO is only showing net8.0-android34.0 and net10.0-android36.0 support however - no net9/android35 combination.

Is it possible to get updated packages for this configuration?

Also, curious to know if anyone here has successfully implemented GooglePay support in a hosted MAUI WebView and has any tips for this?

I have declared the Google Pay intents in the AndroidManifest, Previous attempts with trying to do the WebSettingsCompat.SetPaymentRequestEnabled(settings, true) code didn't seem to make it work properly - but it was with an older Xamarin.AndroidX.WebKit release from 2 months ago.

thanks in advance!
Niall

Dominant language
C#
Stars
318
Forks
73
Avg merge
2d 6h
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/android-libraries

All issues in dotnet/android-libraries

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.