Samples: review SupportedOSPlatformVersion (minimum iOS version) across sample apps

Abierto
  • ¿Algo no está bien?
#628 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp
Área
devtools, mobile

Línea de trabajo

Read the listed MAUI, Avalonia and Uno project files, Avalonia’s Info.plist, and docs/samples/todoapp/; consult framework documentation and release notes for supported iOS and Mac Catalyst versions. Decide and document suitable targets, align the iOS values, and update the documentation. Done when the stated acceptance criteria are met and the three named Build Samples iOS jobs pass on the pull request.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Examples

Summary

Review the minimum iOS deployment target (SupportedOSPlatformVersion) used by the sample apps, and decide whether to raise it.

Background

This was noted while working on #622 / PR #626. SupportedOSPlatformVersion is the minimum OS the app runs on. It is separate from the SDK or Xcode version the app is built with, so it does not block building against newer SDKs. It does control which platform APIs are available without runtime checks, and it can constrain which versions of dependencies can be used.

Current values:

Sample File Setting
MAUI samples/todoapp/TodoApp.MAUI/TodoApp.MAUI.csproj iOS 15.0, Android 21.0, Windows 10.0.17763.0
Avalonia iOS samples/todoapp/TodoApp.Avalonia/TodoApp.Avalonia.iOS/TodoApp.Avalonia.iOS.csproj 15.0
Avalonia iOS samples/todoapp/TodoApp.Avalonia/TodoApp.Avalonia.iOS/Info.plist MinimumOSVersion 15.0
Avalonia Android samples/todoapp/TodoApp.Avalonia/TodoApp.Avalonia.Android/TodoApp.Avalonia.Android.csproj 34
Uno samples/todoapp/TodoApp.Uno/TodoApp.Uno/TodoApp.Uno.csproj not set explicitly (uses the Uno SDK default)

The platform values are not consistent across samples. For example, Android is 21.0 in MAUI but 34 in Avalonia. iOS is 15.0 in both MAUI and Avalonia, but the Avalonia value is duplicated in Info.plist and must be changed in both places.

Proposed work

  1. Confirm the minimum supported iOS (and Mac Catalyst) version for each framework at the versions the samples use (MAUI, Avalonia, Uno), using their documentation and release notes.
  2. Decide on a target for the iOS samples. Consider what the toolkit's client library needs, what current Apple guidance is, and what the samples are meant to show. Samples should reflect what a new app would reasonably choose today.
  3. Decide whether the other platform values (Android, Windows) should be reviewed too, or only iOS. At minimum, document why they differ if they stay different.
  4. Align the values across samples where there is no good reason for a difference.
  5. Keep Info.plist MinimumOSVersion in step with the csproj value for Avalonia.
  6. Consider whether Uno should set the value explicitly so the target is visible in the project.
  7. Check docs/samples/todoapp/ for any mention of minimum OS versions and update it.

Validation

Validate through CI on the pull request: the todoapp-maui / ios, todoapp-avalonia / ios and todoapp-uno / ios-maccatalyst jobs in Build Samples must pass. Triggering workflows with workflow_dispatch on the fork has not been reliable for the macOS jobs, but runs triggered by a pull request work.

Acceptance criteria

  • The iOS minimum deployment target is deliberately chosen, consistent across the iOS samples, and the reason is recorded in the PR.
  • Avalonia's csproj and Info.plist agree.
  • Documentation matches the final values.
  • Build Samples passes on the PR.

Related

  • #622 / PR #626: move macOS sample jobs to macos-26.
  • Follow-up: drop the workload set pin and move to Xcode 26.5 (separate issue). The two changes are independent and should be separate PRs.
Lenguaje dominante
C#
Estrellas
184
Forks
48
Merge medio
12 min
PR fusionados (30 d)
21

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CommunityToolkit/Datasync

Todos los issues de CommunityToolkit/Datasync

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.