Declare TTS_SERVICE <queries> in the plugin manifest so consumers inherit it#641
Open
aki1770-del wants to merge 1 commit into
Open
Declare TTS_SERVICE <queries> in the plugin manifest so consumers inherit it#641aki1770-del wants to merge 1 commit into
aki1770-del wants to merge 1 commit into
Conversation
…utton#449) Since Android 11, package visibility hides TTS engines from apps that do not declare android.intent.action.TTS_SERVICE in <queries>. The README documents the app-side workaround, but apps that miss it get an empty engine/language list. Declaring the query in the plugin's own library manifest lets the Android manifest merger propagate it into every consuming app, making the README step unnecessary.
This was referenced Jul 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the root cause behind #255 / #449. The example app gained its own
<queries>in 43c527c, but apps consuming the plugin still silently fail on Android 11+ unless they discover the README step. Declaring the<queries>intent in the plugin's library manifest lets Android's manifest merger propagate it into every consuming app, sogetEngines/getLanguageswork out of the box.Verification (build-verified locally before submitting; Android 11 / API 30 emulator, Google TTS):
Default Engine: com.google.android.ttsin logcat).flutter build apk --debuggreen before and after.The README guidance remains valid for apps that also query TTS engines directly; with this change it is no longer required just to make the plugin work.