“BloomRPC” cannot be opened because the developer cannot be verified - macos

After downloading BloomRPC from the github repo and running brew cask install bloomrpc, when I try to open the BloomRPC application I get "BloomRPC cannot be opened because the developer cannot be verified." I've tried going to Security and Privacy -> Developer Tools -> and enabling BloomRPC under "Allow the apps below to run software locally that does not meet the system's security policy", but I still get the same error message.
I'm on macOS Catalina 10.15.5. How do I open the BloomRPC application?

You can try to build BloomRPC from source (as they mentioned in their repo) Or you can simply bypass this error go navigate to SystemPreference -> Security&Privacy.
Under General tab, you will see a statement about BloomRPC, click on Open Anyway to suppress the warning and continue to use.

Follow these steps:
Type the following command in terminal - sudo xattr -rd com.apple.quarantine
Add space at the end of command
Drag and drop the app into the terminal window right after the command and hit 'return' key
Enter password and you are good to go.
For Bloomrpc the command will look like this:
sudo xattr -rd com.apple.quarantine /Applications/BloomRPC.app

Related

“STM32CubeIDE” is damaged and can’t be opened. You should move it to the Trash. (On Mac)

After installing STM32CubeIDE on Mac, when we double click on the application, the following error gets shown in a popup window:
“STM32CubeIDE” is damaged and can’t be opened. You should move it to the Trash.
The following command in Terminal does also the trick:
xattr -c /Applications/STM32CubeIDE.app
A Solution:
Open Terminal
Open the application using sudo as follows:
$ sudo /Applications/STM32CubeIDE.app/Contents/MacOS/stm32cubeide
Give root password if required.
The application opens normally.

Why "Watchman crawl failed" error in react-native immediately after updating to macOS catalina?

Trying to run react-native run-ios or build RN project from xcode, as soon as metro bundler starts, this error appears in the terminal:
Loading dependency graph...jest-haste-map: Watchman crawl failed. Retrying once with node crawler.
Usually this happens when watchman isn't running. Create an empty `.watchmanconfig` file in your project's root folder or initialize a git or hg repository in your project.
Error: Watchman error: resolve_projpath: path `/Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA`: open: /Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA: Operation not permitted. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.html.
events.js:183
throw er; // Unhandled 'error' event
^
Error: resolve_projpath: path `/Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA`: open: /Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA: Operation not permitted
at BunserBuf.<anonymous> (/Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA/node_modules/fb-watchman/index.js:95:23)
at emitOne (events.js:116:13)
at BunserBuf.emit (events.js:211:7)
at BunserBuf.process (/Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA/node_modules/bser/index.js:292:10)
at /Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA/node_modules/bser/index.js:247:12
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
This never happened before the Catalina update. I've had an empty watchman config file in the root of my project since the beginning. On first boot post-update, there was a popup in terminal saying something about permissions but i dont remember exactly. there's also a notice in my terminal in visual studio code saying "the default shell changed to zsh" run chsh -s /bin/zsh to change, so i did.
I've tried:
watchman watch-del-all
watchman server-shutdown
adding full disk access to terminal from within system preferences->privacy tab
npm uninstall watchman & npm uninstall -g watchman
You need to grant disk access to watchman. To do this You need to:
Go to System preferences > Security & Privacy then scroll down
Select Full Disk Access
Unlock it and click + button to add new app/tool
Select Macintosh HD in the folders list
Press this combination shift Command . at the same time to see all the directories list
Click opt > brew > bin (watchman is installed in this folder for MacOS Catalina) || usr > local > Cellar > Watchman > 21***** > bin (watchman is installed in this folder MacOS Monterey)
Look for watchman in the list then select it
Here we go, this should fix the issue.
I had the same issue after updating to Catalina. Wez Furlong's answer worked for me, but I had to provide full disk access to watchman in order to run watchman watch-project command without getting "Operation not permitted" error. As part of prior troubleshooting, I also had provided full disk access to Xcode and Terminal (not sure if this also contributed to the fix).
First run watchman watch-del-all
then run watchman shutdown-server fixed my issue
To change the permissions for Watchman regarding the Documents folder, it's under Security & Privacy -> files & folders in the system preferences
My issue was resolved by checking Watchman in the list under Document folder
The error message indicates a permission problem on /Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA.
However, it may be something funky with launchd, so I would suggest:
$ watchman shutdown-server
$ launchctl unload ~/Library/LaunchAgents/com.github.facebook.watchman.plist
$ rm ~/Library/LaunchAgents/com.github.facebook.watchman.plist
$ watchman watch-project /Users/vorousjames/Desktop/Development/TicTacWHOA/app/TicTacWHOA
and see if that works or shows more context.
Cross linking back to an issue in our GitHub tracker:
https://github.com/facebook/watchman/issues/751
You need to change something its works for me. follow only following steps:
1. Go to System preferences > Security & Privacy then scroll down.
2. Select Full Disk Access.
3. Look for all watchmen on the list.
4. check(Mark) all Folders in all watchman files.
5. then go to vs code.
6. rebuilt your code.
I hope it will work smoothly
Try to change the directory of your project. I had mine on desktop and was getting that error, moved to the home folder and the error is gone
Just uncheck the repeated boxes in Mac:
System Preferences -> Security and privacy -> Privacy
For me above scenario didn't work, so I tried with different solution which solved the problem for me. (I am using MacBook Pro, chip: Apple M1 pro)
At first you have to update the setting of your Mac OS
System Preference >> security & privacy >> privacy tab >> Full disk access >> click on the lock icon >> checkmark for terminal
Sometime using this steps you are able to resolve the issue, but after this, if you are still facing issue, please use this link: #1030 (comment)
on macos. brew uninstall watchman
it works for me
npx react-native start --port=8088 resolved mine
There is only one solution at the moment. Move your project from the "Desktop" or "Documents" folder to the main folder (~/). None of the other ways worked for me.
This is because MacOS now asks for permissions for these folders (example in the image below). I guess this hasn't been added to the watchman yet.
As a temporary workaround, you can move your project to your home folder and it should run successfully.
To open your home folder, press Command-Shift-H.
(As of June 2022, there seems to be an issue with the 2022.05.30.00 version of Watchman, and this temporary solution is the only way I have been able to get around the issue.)

How to copy intl.so to /usr/lib/php/extensions

I wanted to try Moodle (LMS) on my computer. It requires intl extension.
I used sudo port install php71-intl and successfully installed php71-intl. But it also installed php71 and other dependencies on /opt/local/.
I am using Mac built-in php. Its directories are
/usr/lib/php/extensions/no-debug-non-zts-20160303
/usr/bin/php
I intended to copy the /opt/local/lib/php71/extensions/no-debug-non-zts-20160303/intl.so to /usr/lib/php/extensions/no-debug-non-zts-20160303. But terminal said Operation not permitted.
I tried sudo pecl install intl but failed with make error.
This method sudo port install php71-intl can install the intl.so successfully but in its own direcotry.
So how I can copy the intl.so? Thank you!
You have to disable SIP to do that. First, restart your Mac and before OS starts up, hold down Command-R and keep it held down until you see an Apple icon and a progress bar. Release. This boots you into Recovery. From the Utilities menu, select Terminal and at the prompt type exactly the following and then press Return: csrutil disable
Terminal should display a message that SIP was disabled. From the menu, select Restart. You can re-enable SIP by following the above steps, but using csrutil enable instead.
Find this file "environment.xml" and comment all lines that have "intl" and reload the page. Continue button appears and installation completes without any error. My instance started working like charm, I use it to test out and create courses with SCORM packages, no errors yet.
environment.xml file is located in "admin" folder of moodle directory

hipchat password not retrieved from credential storage

I am trying to use the OSX Hipchat desktop client v 3.3 (193). I have OSX 10.10.3. I have followed the instructions suggested by Hipchat support https://help.hipchat.com/knowledgebase/articles/166483-mac-beta-client-clearing-preferences
Close your HipChat app
Open Keychain Access (search for Keychain Access in Spotlight)
Click the "login" keychain in the top pane of the left sidebar
Click "passwords" in the bottom pane
Search for "hipchat" using the search box in the upper right and remove any associated entries from the list
Open Terminal (search for Terminal in Spotlight)
At the command prompt, enter the following commands:
defaults delete com.hipchat.HipChat
rm ~/Library/Preferences/com.hipchat.HipChat.plist
rm -rf ~/Library/Caches/com.hipchat.HipChat
rm -rf ~/Library/HipChat
rm -rf ~/Library/Application\ Support/hipchat/
I am still getting this error
I am trying to figure out where on my computer an extra credential to delete must be hiding, or what permissions I have messed up.
I have access through the web interface but I would prefer to use the native app.
I had the same issue and exchanged email with Support. They believe there is a bug in 3.3 involving port settings which will be fixed in the next update which is "due soon." None of the above suggestions worked.
I had to reinstall 3.2.1 and that fixed the problem.
If you haven't already, try:
quit hipchat
restart computer
reset your HipChat password through the web interface
attempt to sign in to app

Running a cocoa app which requires keychain access from root terminal

I am trying to run a cocoa app KeychainTesterApp while I am logged in as root (sudo su).
Here are the steps:
Open terminal -> type sudo su -> Enter password.
Now, I want to open the app , so I do this: sudo -u username open KeychainTesterApp.app. The app starts up, except when I try to do anything related to the keychain I get the error Keychain not found - "A keychain cannot be found to store."
Any thoughts?
Thanks in advance.
The issue you're having above might be that running:
sudo -u username open KeychainTesterApp.app
Will not open the app as root. To open a Cocoa app as root, run the actual executable as sudo:
sudo "SimpleKeychainExample.app/Contents/MacOS/SimpleKeychainExample"
I'm not sure why the app cannot find the keychain you're looking for. Posting a code example from where that app is opening the Keychain might help clarify the question.

Resources