---
title: "Comment by Apps by Mo on \"Downloaded Is Not Selected: Managing Whisper and Qwen Models in a Native Voice App\" | Hashnode"
description: "The installed versus selected split is the one I learned the hard way. In one of my Mac apps a background job stayed pointed at a model that could not do that j"
url: "https://hashnode.com/posts/downloaded-is-not-selected-managing-whisper-and-qwen-models-in-a-native-voice-app/6af119ffc00574d395f8766d/comment/6af1c878db22570f0bdfd56f"
---

[Discussion](https://hashnode.com/posts/downloaded-is-not-selected-managing-whisper-and-qwen-models-in-a-native-voice-app/6af119ffc00574d395f8766d)

Comment [Downloaded Is Not Selected: Managing Whisper and Qwen Models in a Native Voice App](https://hashnode.com/posts/downloaded-is-not-selected-managing-whisper-and-qwen-models-in-a-native-voice-app/6af119ffc00574d395f8766d)

[Apps by Mo](https://hashnode.com/@appsbymo)

[Nov 9](https://hashnode.com/posts/downloaded-is-not-selected-managing-whisper-and-qwen-models-in-a-native-voice-app/6af119ffc00574d395f8766d/comment/6af1c878db22570f0bdfd56f)

The installed versus selected split is the one I learned the hard way. In one of my Mac apps a background job stayed pointed at a model that could not do that job. I removed it from the recommendations and added a warning badge, but installs that had already picked it kept failing quietly for weeks. What fixed it was a launch migration that moves existing selections, plus one runtime resolver every caller goes through, so “selected” can’t drift away from “usable”.
