ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Mobile & games · #xamarin
Problem Description Xamarin’s HttpClient relies on platform‑specific handlers (OkHttp on Android, CFNetwork on iOS). The default connection pool is opaque; no public API exposes its size or timeout. When many concurrent requests are issued, the pool may silently drop connections after a timeout, leading to intermittent failures. Unresolved Decision For proje
The primary objective is to guarantee that a Xamarin.Android application targeting API level 33 can successfully install and launch on Android 13 devices. The current build process preserves the legacy READ_EXTERNAL_STORAGE permission declared in the app’s manifest, yet Android 13 requires the new READ_MEDIA_IMAGES (and related media permissions) for media a
A Xamarin.Forms 5.x solution uses types that are only accessed via reflection for DI, JSON serialization, or attribute scanning. The managed linker is typically disabled in Debug and enabled in Release, which can strip metadata that is not statically referenced. Two documented mitigation approaches exist for this behavior. Applying [Preserve(AllMembers=true)
Problem Statement The goal is to configure Xamarin’s HttpClient so that a transient network timeout does not cause the same non‑idempotent POST to be sent twice, which would create duplicate records on the server. Xamarin’s HttpClientHandler provides no built‑in retry mechanism, so any custom retry logic must be added by the developer, but the framework does
Goal Confirm whether a Xamarin.Android activity declared with [Activity(Exported = true)] and no intent filter remains accessible to any installed app after manifest merger on Android 12 (API 31) or higher. Constraint Android 12 requires an explicit android:exported declaration for components with intent filters, and library manifest merger can override the
Authentication Flow Failure In a Xamarin.Forms application utilizing MSAL.NET for Azure AD authentication, the application is designed to prioritize silent token acquisition to maintain a seamless user experience. The goal is to implement a least-privilege security model where tokens are refreshed automatically until they expire or are revoked. Credential Ex
Goal I want a Xamarin app (Android and iOS) to post local notifications that appear silently in the shade or Notification Center, with no sound, vibration, banner, or badge. The design intent is a low-priority status update that the user can check at their convenience. Constraints and uncertainty On Android, the plan is a NotificationChannel with importance
android