The uses-permissions tag only grants your app to use functions which requires this permission, when the protection level of the permission is normal, or allow your to prompt the user to grant the permission either from within your app or manually from the app settings, if the permission protection level is dangerous.
Declaring the permission using the uses-permission tag, will not prompt the user to grant the permission, you have to programmatically do it, Appinventor provides an easy approach to do that by invoking the Form.askPermission(String, PermissionRequestHandler) method.
However, for your case, you will not require to prompt the user to grant the permission, because it’s protection level is already normal, you can safely use the methods that needs this permission after declaring it in rush’s AndroidManifest.xml, as you did.
…umm, yeah. That’s it. This is not a major release after all.
Bug fixes
Fixed the inconsistent behavior of property-type blocks. [ref]
Fixed the issue where the extension’s assets and the license file won’t get compiled within the AIX file.
Fixed the unnecessary invalidation of caches while building the extension. This resulted in slightly increased build times.
Fixed the issue that sometimes caused the Java warning to show more than once.
Fixed some other minor issues.
Internal changes
There’s been quite a few improvements in the working of the Rush installer (a.k.a rush-init). You, as an end-user, won’t notice many changes (expect the perky progress bar ), but this will lay the foundation for an upcoming feature that will allow you to upgrade Rush without leaving your terminal.
Installation
If you already have Rush installed on your computer, simply download the Rush installer for your OS from the latest release and run it.
If you don’t have Rush installed, follow this wiki to install it.
It’s likely that’s just boilerplate code you get, nothing special. Larger extensions will take a longer amount of time to build (normally 5 to 8 seconds for me), as usual.
With the previous release (v1.1.1), an issue cropped up that caused the APK creation to fail if the extension used any external library.
So, if you recently upgraded Rush to v1.1.1, I urge you to upgrade it to v1.1.2 ASAP.
Bug fixes
Fixed the issue that caused APK creation to fail when using external libraries.
Installation
If you already have Rush installed on your computer, simply download the Rush installer for your OS from the latest release (v1.1.2), and then run it (it will only update the affected files).
If you don’t have Rush installed, follow this wiki to install it.
Can you help me?
I followed all the steps to install Rush, then I went to build, there is practically nothing there, I just created it and when I went to build it, it returned these errors.
Recently I conducted a survey, which very few participated in. Previously I was trying to convince @Shreyash to include the Android R Prebuilt Platform SDK in Rush, which would allow extension developers to develop extensions for Android R. Currently if you type Build.VERSION_CODES. into IntelliJIDEA (or an IDE with “code completion”), Build.VERSION_CODES.R will not appear. That is because Rush is using the The Android Q Prebuilt Platform SDK, which App Inventor uses since they target Android Q. @Shreyash will not be including the Android R Prebuilt Platform SDK in Rush, but instead stick to App Inventors cycle (which is slow).
Although it’s at his discretion to include the Android R Platform SDK or not, you could of course upgrade it locally by yourself. There are two ways to do this.
Globally
Per-project
To make sure you understand the process, this is only meant for IDEs which have “code completion” for Java (and when building with Rush, since it checks methods against dependencies), such as IntellIJIDEA. The “dev-deps” directory is meant for development dependencies and aren’t included in your final extension, they are simply there so that your IDE can use “code completion,” which makes it easier for you to code!
Globally
This is a good guide if you want to replace the “android.jar” automatically for future created projects. If you have previously created projects, follow the “Per project” guide.
Locate the folder that Rush has created; “C:\Users\user\AppData\Roaming\rush”
This was created with v1.1.0. You will have to find the directory which you unzipped Rush into if you still use anything below v1.1.0.
Now go into “dev-deps”
This is where development dependencies are located, they aren’t included with your extension.
Download the Prebuilt Platform SDK from one of the following links