Repository navigation
Format and update AndroidManifest.xml - #45
Conversation
|
Which app was unable to use VoxSherpa as a TTS engine and was crashing/failing to bind to the TTS service? I tested both the current version and your PR build with Android System TTS and @voice, and both work correctly for me. I just want to know which specific app was affected. |
|
I tried to use IReader app and LNReader app, both use tts engine from android to read books |
|
If you are not sure, I return that permission that was remove , and just add that service intent, I think that will fix my issue (not sure need to try again and text again I think) |
|
I searched everywhere and don't see any android.permission.BIND_TEXT_TO_SPEECH_ENGINE in internet and offical android docs |
|
This is my app https://github.com/IReaderorg/IReader I was searching for a good offline tta engine, and found yours tried and found it's not working then find issue In your code |
|
I don't know much about the Android TTS service configuration, but I noticed these two lines: "android.intent.action.TTS_service" Why are both needed? Is "TTS_service" required for any specific app or compatibility reason? |
the whole issue was your app permissions doesn't exists at all |
|
now everything is working fine, I removed that extra line |
|
just removing the permission is enough, the code is ready for merge without any extra line |
1. Fix Critical Manifest Bug Blocking TTS Service Binding
In
AndroidManifest.xml(line 105),VoxSherpaTtsServicedeclared an invalid binding permission:Problem Analysis
android:permissionattribute on a<service>tag enforces that any client application attempting to bind to the service must hold that specific permission.android.permission.BIND_TEXT_TO_SPEECH_ENGINEdoes not exist in the Android OS framework. Consequently, no client app (such as IReader, Chrome, etc.) can ever hold or be granted it.TextToSpeech(context), Android'sActiveServices.javaverifies whether the calling app holdssInfo.permission. Because the client lacks this non-existent permission, Android aborts the bind operation and throws:Resolution
Remove the
android:permissionattribute fromVoxSherpaTtsService. Standard Android TTS engines (e.g., Google TTS, Samsung TTS, eSpeak, RHVoice) do not require binding permissions so third-party applications can bind directly.