-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
installation fails on Android 12: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED #12
Comments
still there |
I hope this gets fixed sometime soon. Just using VOSK in Dicio it seems like a really great model. I'd love to use it in day to day tasks. |
Can be closed. I fixed this. |
Great! waiting for the new release apk
|
Eager to get this new release 👀 I bet others are too: |
The problem is getting in touch with developers to fix up the issues with the application. As I currently have no way to contact them. |
This can be closed now |
Not until the release.
|
I got the same error on Pixel 4a, I tried to compile from source via Android Studio and it runs |
I built from 6a71977 using Android Studio, then installed one of the resulting I used the app to install some models and then invoked via AnySoftKeyboard's voice typing(?) key/button. A dialog box does show up as a voice prompt(?), but after speaking, I see the message [1] I think it's 12L, but I'm not sure how to tell for sure -- I'm using some 12L features, but the info I see via |
Just failed on Android 13. A new release would be great. |
@SunnyDaze I've made an unofficial apk if you are interested, it works very well. tested on Android 13 |
$ adb install -r vosk-android-service-0.3.42.apk
Performing Streamed Install
adb: failed to install vosk-android-service-0.3.42.apk: Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED: Failed parse during installPackageLI: /data/app/vmdl910797472.tmp/base.apk (at Binary XML file line #106): org.vosk.service.VoskRecognitionService: Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present]
The text was updated successfully, but these errors were encountered: