I use appinventor sources to create extensions and already have knowledge to create extensions.
But sorry I am quite busy in making an extension which will be released in the middle of the month.
That’s why I asked @Ken to give it a try.
Please don’t shoot. On a similar note, could someone help show me how they handle services when building extensions. I’v’e tried using inner classes implementing the service but not sure that’s such a good idea.
android.permission.BIND_NOTIFICATION_LISTENER_SERVICE cannot be asked from the app itself because it must be defined with the <service> element by the android:permission attribute in the AndroidManifest.xml.
The problem is that I don’t think this can even be asked because Kodular adds services and elements with attributes to the AndroidManifest.xml after the app has been launched. There’s no definitive way as far as I know to do it. Even if you run the app and extract the .APK, it will still not work. However this can vary from situation to situation as I haven’t really went into much detail.
@akshay_gadekar However hope should not be lost. Define the permission in your extension @UsesPermissions("android.permission.BIND_NOTIFICATION_LISTENER_SERVICE"). When you build your extension, obviously upgrade it in your app and compile your .APK. It won’t ask you for the permission, but you should be able to find it somewhere. On an S7 Edge, you’d navigate like this Settings ~ Apps ~ 3-dotted Menu ~ Special Access ~ then Notification Access. You’d find your app there and enable it. I’m not sure if it’d work, but it’s a shear attempt at something good.