Skip to content

Latest commit

 

History

History
31 lines (26 loc) · 7.68 KB

issues-3.2.0.md

File metadata and controls

31 lines (26 loc) · 7.68 KB

3.2.0 issue-resolution ledger

This ledger covers exactly the 19 open issues in scope for the 3.2.0 release. “Resolved” below means the issue has a code/test/documentation disposition; it does not claim that every OEM's system wallpaper UI was physically validated.

Issue 3.2.0 disposition Evidence and remaining boundary
#6 — CenterCrop Resolved with explicit scale selection instead of a fixed crop. WallpaperScaleMode.centerCrop, fitCenter, center, fill, and stretch are implemented by BitmapTransformer; geometry is covered by BitmapTransformMathTest.
#10 — File.toPath() crash Resolved by using Android-compatible stream/file handling rather than Java NIO path APIs. WallpaperSourceLoader and BoundedSourceOpener accept readable file sources with bounded streams; source errors are returned as structured failures.
#14 — file images not accepted directly Resolved with WallpaperSource.filePath. Static/video requests accept file paths directly; the example and README show passing a path from the app's own picker/cache without requiring flutter_cache_manager.
#15 — WorkManager platform exception Resolved for direct static work; UI flows are explicitly separated. StaticWallpaperEngine.applyDirect has no Activity dependency. Cropper/picker/live UI return foregroundRequired without a foreground activity; background rules document the boundary.
#16 — second call fails in succession Resolved by serialized mutation handling. OperationQueue runs apply, video, and renderer configuration work FIFO; OperationQueueTest covers ordering, rejection, and exactly-once completion.
#19 — both screens unreliable Resolved with combined-flag apply, serialized fallback, and per-target results. StaticWallpaperEngine preserves home/lock outcomes and fallbackUsed; ResultContractTest and Dart result tests protect partial-result semantics.
#22 — unwanted return to the previous/home screen Resolved by removing package-side delayed navigation from the structured engine. 3.2 performs no automatic navigation. goToHome remains only as a source-compatible request field and is intentionally ignored; applications own any foreground navigation after a verified result.
#23 — Android 13 app restart Mitigated by activity-safe lifecycle handling and serialized callbacks; not represented as a false Android-version guarantee. The plugin keeps only a weak, current activity for UI paths and keeps direct work headless-safe. OperationQueueTest and result-contract coverage exercise lifecycle/error completion paths. Device/OEM regression verification remains app-specific.
#24 — foreground app/service remains after video set Resolved by a wallpaper-service lifecycle with no foreground service. VideoLiveWallpaper uses asynchronous preparation, visibility-aware playback, muted audio, and one release path; VideoStateMachineTest covers pause/resume/release behavior.
#25 — MIUI 14 live wallpaper resets screens Documented unavoidable Android/OEM limitation. Android's live preview owns confirmation and target selection. The plugin reports previewOpened/awaitingUserConfirmation rather than a false apply result; see OEM behavior. No Xiaomi physical-device validation is claimed.
#26 — file image stretches Resolved with selectable, documented image scale modes. BitmapTransformer applies the requested static scale mode; BitmapTransformMathTest covers crop/fit/center/fill/stretch geometry.
#28 — live-wallpaper feature reduces Play support Resolved with an optional manifest feature. android.software.live_wallpaper is android:required="false"; packaging tests assert the optional feature and permission surface.
#29 — cannot override async_wallpaper name Resolved with app-overridable service resources. Consumers can override the video/OpenGL labels and description documented in permissions, distribution, and branding.
#30 — success toast shown too early Resolved by removing package-owned notifications and returning structured statuses. No plugin toast is emitted. WallpaperOperationResult distinguishes applied, previewOpened, and awaitingUserConfirmation; facade/result tests cover that distinction.
#31 — plugin name shown in the live-wallpaper bottom sheet Resolved with service-label and description overrides. Override async_wallpaper_video_live_wallpaper_label, async_wallpaper_opengl_live_wallpaper_label, and async_wallpaper_live_wallpaper_description in the consuming app.
#33 — live wallpaper applied to both screens Documented unavoidable Android/OEM limitation. The system preview, not the plugin, selects a live-wallpaper target. The request target is intent only for that UI flow; the plugin cannot force a lock/home/both outcome across OEMs.
#34 — live wallpaper removes or changes lock screen unexpectedly Documented unavoidable Android/OEM limitation. The same live-preview target limitation applies. The API does not claim applied merely after opening system UI; apps must explain the OS preview choice to users.
#35 — Reply already submitted Resolved with exactly-once operation completion. OperationQueue.OnceCompletion guards every queued callback, including shutdown/rejection paths; OperationQueueTest covers the contract.
#39 — OpenGL live background Resolved with a bounded GLES2 wallpaper service and typed request API. OpenGlLiveWallpaper, GlRenderer, and ShaderProgramValidator implement the flow; ShaderContractTest covers request validation. Actual GPU compile/link and OEM preview behavior still require device verification.

What remains intentionally outside a code-only claim

The live-wallpaper rows above are not closed by pretending that a system preview is an applied result. Android does not offer a cross-OEM API to force a live wallpaper onto home, lock, or both displays. The plugin reports the distinction, exposes device capabilities, and documents the limitation so consuming applications can make an informed UX decision.

For any reopened report, include the capability snapshot, structured result including target statuses/error values, source kind, strategy, device model, Android release, and OEM build. This lets an OEM-specific behavior be separated from an input, policy, or lifecycle failure.