No habia visto este tema, tengo la misma problematica, pero es especificamente con las extensiones NotificationStyle y ItoO, porque al eliminar dichas extensiones la apliacion deja de enviar este error, hice una pequeña app de prueba y si es por las extensiones
The kio4.service.aix extension also had problems with FLAG_IMMUTABLE or FLAG_MUTABLE, I have updated it, I hope it works.
I have deployed a temporary server where you can test the issues related to FLAG_IMMUTABLE in the built-in components here. Extension authors will still need to separately update their extensions to be compatible with Android S.
2 Likes
Thanks for the efforts. I am making a simple SMS based app to act as a paging app. I uploaded my .aia file to nb190a-bugfixes.ai2-ewpatton... server but I am getting the same Targeting S+ version 31 and above)... error. The version of emulator I am using is 2.65u
I attaching the .aia file here for reference.
KayKayPagingReceiver.aia (719.6 KB)
MIT knows about the bug in the SMS component since nb190 and Companion 2.65.
The Texting component will be fixed soon. Please be patient. 
3 Likes
Did you install the companion version provided by that server? It should be 2.65d1u. Otherwise, you have the production companion which will still have the bug.
I installed the companion version provided by that server by scanning the qr code, downloading the apk and then updating the app on the phone but it shows the version 2.65.
I uninstalled the companion app and installed the downloaded apk also but in that app the version shown is 2.65.
The link from which I downloaded the APK is :
However, by update or even by fresh install the version of the app is shown as 2.65.
Yes ...
but where is the problem?
E W Patton has deployed a temporary server with the fix and its companion app is supposed to have the version 2.65d1u. While testing my app on this sever, I see that the version of the companion app from the temporary server is still 2.65 and not 2.65d1 or 2.65d1u
As I said:
The VersionName is 2.65 but the Companion app is 2.65d1 or 2.65d1u:
Ok, I will wait for the issue to be fixed but my comment was in response to this original comment on the thread
Did you try to build the APK on the test server, install it ... ?
If not, do it and report if the error occurs again. It doesn't do that for me on Android 12+.
Thanks for the suggestion to build the APK. I can confirm that the fix works for me for sending message directly via the app.
I downloaded the companion app from the link given on temporary server :
The version of the companion app as shown in my phone :
The permission denied message received when the project is being tested via companion app.
I have given all the permissions to the companion app.
Yes ...
although SEND_SMS permission is declared in the Manifest & enabled in the Settings.
Correction:
SEND_SMSpermission is NOT declared in the Manifest of the Compannion app (2.65d1or2.65d1u). I checked it again! (Apparently I had the manifest of the regular Companion app open as well.)
Hmm. I think one of my changes may have broken that. I'm currently in the air on my way home from a conference, but I should be able to have an update out tomorrow.
1 Like
Well through the magic of satellite internet I've updated the server. The new companion number should show 2.65d2u.
4 Likes
Hi and sorry for a possibly stupid question but where can i download the version 2.65d2u? The qr-code is only for 2.65d2 and i cannot find a link for download.