-
Notifications
You must be signed in to change notification settings - Fork 569
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: dotnet/android
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1878a87228
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: dotnet/android
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 51a138deee
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 5 commits
- 13 files changed
- 2 contributors
Commits on Jan 8, 2026
-
[coreclr] fix string
runtimeconfig.jsonvalues (#10669)`prop.Value.GetRawText ()` returns a string value `foo` as `"foo"`. Let's instead switch on `JsonValueKind` and handle each type appropriately. The existing `AppContextTests` should verify this when we enable the `RuntimeConfig` category.
Configuration menu - View commit details
-
Copy full SHA for c4b72d3 - Browse repository at this point
Copy the full SHA c4b72d3View commit details
Commits on Jan 9, 2026
-
[tests] ignore 404 on
AndroidMavenLibrary_AllDependenciesAreVerified(#10666) Test randomly fails with: (_MavenRestore target) -> Xamarin.Android.Bindings.Maven.targets(28,5): error XA4236: Cannot download Maven artifact 'androidx.core:core'. Xamarin.Android.Bindings.Maven.targets(28,5): error XA4236: - core-1.9.0.jar: Response status code does not indicate success: 404 (Not Found). Xamarin.Android.Bindings.Maven.targets(28,5): error XA4236: - core-1.9.0.aar: The process cannot access the file 'C:\Users\cloudtest\AppData\Local\dotnet-android\MavenCacheDirectory\google\androidx.core\core\1.9.0\core-1.9.0.aar' because it is being used by another process. Let's make this `Assert.Inconclusive()`. I also fixed where the test wasn't building the `collection` project.
Configuration menu - View commit details
-
Copy full SHA for 31cc7b1 - Browse repository at this point
Copy the full SHA 31cc7b1View commit details
Commits on Jan 12, 2026
-
[tests] improve assertions in
CancelRequestViaProxy()(#10671)This test is flaky, but it currently has a terrible error message as "1": Mono.Android.NET_Tests, Xamarin.Android.NetTests.AndroidMessageHandlerIntegrationTests.HttpClientIntegrationTestBase.CancelRequestViaProxy / Debug Error message 1 Stack trace at Xamarin.Android.NetTests.HttpClientIntegrationTestBase.CancelRequestViaProxy() in /Users/runner/work/1/s/tests/Mono.Android-Tests/Mono.Android-Tests/Xamarin.Android.Net/HttpClientIntegrationTests.cs:line 166 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) Let's improve the assertion message, in general, and that might help diagnose the flakiness in the future. This shouldn't alter the behavior of the test, just the assertion message.Configuration menu - View commit details
-
Copy full SHA for 7899160 - Browse repository at this point
Copy the full SHA 7899160View commit details -
[illink] set
$(StartupHookSupport)=false*only* for Release mode (#……10670) Context: https://github.com/dotnet/runtime/blob/242f7b23752599f22157268de41fee91cb97ef6c/docs/design/features/host-startup-hook.md .NET has a concept of a "startup hook", which appears to work fine on Mono if you set: env.txt DOTNET_STARTUP_HOOKS=StartupHook (MSBuild) <StartupHookSupport>true</StartupHookSupport> <RuntimeHostConfigurationOption Include="STARTUP_HOOKS" Value="StartupHook" /> The startup hook is a managed assembly with a static method, in the "global" namespace: class StartupHook { public static void Initialize() { // ... } } When the runtime starts, it will call `StartupHook.Initialize()` before any other managed code is executed. `dotnet watch` (Hot Reload) relies on this feature. I added tests to verify startup hooks are called on Android for all runtimes. * [coreclr] call `System.StartupHookProvider.ProcessStartupHooks()` This feature only works on CoreCLR if you have a `static void Main()`, which we do not on Android. For now, I called the `StartupHookProvider` directly with System.Reflection. We can address in dotnet/runtime in the future.
Configuration menu - View commit details
-
Copy full SHA for b2332ca - Browse repository at this point
Copy the full SHA b2332caView commit details -
Configuration menu - View commit details
-
Copy full SHA for 51a138d - Browse repository at this point
Copy the full SHA 51a138dView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 1878a87228...51a138deee