I use RPi3 with Android Things 0.5.1. Although I have in my AndroidManifest.xml the permission:
<uses-permission android:name="com.google.android.things.permission.MANAGE_INPUT_DRIVERS" />
I get the exception:
java.lang.SecurityException: Caller lacks required permission com.google.android.things.permission.MANAGE_INPUT_DRIVERS
Anybody got working this permission on 0.5.1?
That permission is currently marked as a dangerous permission, which would typically require granting at runtime by the user on standard Android. In Android Things, these permissions are granted automatically, but only on device boot. You need to do one of the following to give that permission to your app:
Reboot the device after the first installation. This will grant the permission on restart.
Install the APK manually using adb install -g <APK> the first time. This flag grants all requested permissions on install, so you can avoid the reboot.
Upgrade to Android Studio 3.0, which will automatically grant these permissions on install for you so you don't need to do either #1 or #2.
Related
This is the first time I am installing flutter on the mac. I have followed all the steps that are told in flutter.dev. After setting up the path in .zshrc, I get this strange error.
The flutter tool cannot access the file or directory.
Please ensure that the SDK and/or project is installed in a location that has
read/write permissions for the current user.
This is the .zshrc file looks like.
After running flutter doctor getting this.
Thanks in advance.
I encountered this issue when moving my project from windows to a Mac folder. It seems to be an issue with some extended attributes. Using the below command worked for me.
sudo xattr -c -r <project_folder_path>
I'm not sure about this but try it. go to the folder where you installed Flutter, click the folder with to fingers which will show options. got to {Get info} look down at the Sharing & Permission, make sure your current user has read and write.
I just hope this will fix your problem
I downloaded gActions CLI on windows x64 bit machine. after issuing the login command and pasting the the browser link i get the below error:
This app is blocked
This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.
Was having the same issue when I downloaded the gactions script manually from this page.
I was able to resolve the issue when I instead downloaded the utility from npm:
npm i -g #assistant/gactions
Solution for Mac/Linux system, not verified on Windows.
You have to provide proper permissions while running the command.
Example : - sudo gactions login
This worked for me too, but only after I deleted the gactions.exe file I had earlier downloaded (and had set a path environment variable for).
This worked for me
gactions login --actions-builder-only
I installed on an M1 Mac using brew install gactions
I've been trying to solve this issue for two weeks and cannot seem to find a solution, it only happens on Appium desktop with automationName set to UiAutomator.
I changed ownership of the /tmp folder from Root to user and set permissions to 777 but still facing the issue: I cannot change the file's permission since it's a temp folder and its name keeps changing every time I run a new appium session.
This is the error message:
An unknown server-side error occurred while processing the command. Original error: The application at '/tmp/.mount_app.Ap8xEj5P/resources/app/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk' is not writeable. Please grant write permissions to this file or to its parent folder '/tmp/.mount_app.Ap8xEj5P/resources/app/node_modules/appium/node_modules/appium-uiautomator2-server/apks' for the Appium process, so it could sign the application
You could try to grant permission on /users/username/node_modules, /usr/local or /usr/bin. I ran in the same problem while trying to use UIAutomator2 on macOS and granting permissions gradually. Also, if you have the latest version of Appium, you need to switch to UIAutomator2, starting v12.1 UIAutomator is no longer supported.
Another hint: don't mix UIAutomator with UIAutomator2, check that you are trying to launch with correct capabilities
This bug plagued me for weeks before resolving it. The issue ended up being my Java version. I did NOT have to modify signing or read / write privileges on the file in question.
JAVA_HOME and Path environment variables were both pointing to Java 12. I needed to install jdk_1.8.0 for Java 8, and update JAVA_HOME and Path to point to Java 8. More info and possible solutions can be found on my GitHub issue that I opened with Appium devs:
https://github.com/appium/appium-desktop/issues/1080
I downloaded 8.9.4 LTS Node.js for macOS (x64).
Then I went to: http://docs.phonegap.com/getting-started/1-install-phonegap/desktop/ and followed the instructions.
I had just finished dragging PhoneGap into my applications folder and when I tried to open the application, this popped up:
The most important detail from the image seems to be:
Error: EACCES: permission denied, open '/Users/bruce/.config/configstore/insight-phonegap.json' You don't have access to this file." Any help with solving this would be greatly appreciated! (same thing happened when I tried to use the CLI)
This is a user permission issue.
User other users (such as root) with privilege to write to .config/configstore/ folder can solve the problem
I have just updated my AIR SDK from version 23 to 25.
When running the command mxmlc, the following error occurs:
Error: Unable to access jarfile /../lib/mxmlc-cli.jar
Solution 1:
Make sure you have downloaded the Flex SDK and not the AIR SDK.
In the download page, there's link specifying:
Flex users will need to download the original AIR SDK without the new compiler.
Solution 2:
When the Adobe AIR SDK is installed it is sometimes installing files with wrong permissions.
The mxmlc-cli.jar file your lib directory probably has a permissions issue.
Try giving this file full permission and making sure it's not read only and everything should work fine.
If you are using Windows, just right click the files and set up the proper permissions in the security tab, and make sure the file is not read only.
If you are using Unix / Linux, run the following:
$ su -
# cd [AIRSDK install directory]
# chmod -R go+rx *
If you are using Mac OS:
Click the mxmlc-cli.jar file or to select it.
From the File menu, select Get Info. One of the windows shown below
appears. Click the disclosure triangle next to Sharing & Permissions
to display the file's permissions.
Click the lock and authenticate with an administrator account. Use
the menus next to users and groups to change the permissions.
This is an old one, but I've faced this problem several times and the fix is really minor.
You have to edit mxmlc or compile.
In the file there is a row which should be changed to:
SCRIPT_HOME=`dirname "$0"`
The error comes from missing " " around the $0.