On my Galaxy s24Ultra (Android 14) i can not enable the Notifications for App Inventor Companion. The phone is about half a year old, and I only noticed this now because I haven't used notifications before. I have deleted and reinstalled Companion multiple times. I also installed Companion from the Play Store, but nothing.
Companion is also not in the list of apps for notifications.
Sorry if I'm being annoying, but I'm just stuck. I've now tried a Galaxy Note 20 Ultra (Android 13), and I still can't enable the notifications. But it works on a Motorola e20 (Android 11). Likewise with a Galaxy A12 (Android 12).
What do I need to consider with a device running Android 13 or higher?
It seems none of us quite understand what it is you are trying to do, explain a bit more about why your are attempting to enable notifications (explain what you mean by this) for the Companion app.
Thank you for your interest. I tried programming with MelonNotification, but my phone never showed a notification. Then I found out that Companion doesn't allow notifications and I can't enable them either. Hopefully, the picture will clarify what I mean.
The .apk naturally allows enabling notifications, but I can't test it like this with Companion. I have tried it with 5 phones and noticed that on phones with Android 13 and higher, it is not possible to enable notifications for Companion. The last version was 2.67. With all subsequent versions, I can no longer enable notifications. On phones with Android lower than 13, it still works with the current Companion.
Yes, because notifications from android 14+ require additional permissions in AndroidManifest.xml that Companion does not include. Test notifications in compiled apk.
Sorry, but this is beyond my capabilities. I'll manage by testing my app as an .apk. Clarity was important to me because I always assumed I was doing something wrong. Thank you very much for your help, guys.
@ewpatton The Companion version that can be downloaded from the server contains more permissions. I think there is nothing to stop it from including additional "post notifications".
You're technically correct, but the permissions that are included are the union of all of the permissions required by the built in components. We selectively remove permissions for the Play Store build to comply with Google's requirements rather than adding them to the version on the website.
The texting component does have the feature, when the app is in the background and a message comes in, then a notification will be displayed, so that feature requires post notification permission...
Finally if ReceivingEnabled is set to 3, messages will be received when the application is running and when the application is not running they will be queued and a notification displayed to the user.
It's possible that the documentation is wrong. I haven't used an Android device as my daily driver in a while. If there's a permission needed for showing a notification I expect that the companion isn't doing it.
I have been working on a branch to bring local notifications to Android and iOS. It's not ready for production but eventually if the permission is needed it will be added.
I will have to double check. It really depends on what App Inventor core components are doing. If somehow it works, then I would not consider it forgotten. If it doesn't work, then yes it is an oversight.