Mac OS Mojave can't open terminal from Cyberduck because that Not authorized to send Apple events to Terminal - macos-mojave

Mac OS Mojave can't open terminal from Cyberduck because that Not authorized to send Apple events to Terminal.

This issue is tracked in #10475 and is fixed in the current snapshot build.

Related

“launchPackager.command” can’t be opened

Just updated my Mac to the official release of Ventura, and I cannot launch my application via react-native run-ios.
Expected behavior:
running react-native run-ios will launch an Xcode simulator and a terminal window with Metro running.
Current behavior:
Xcode simulator opens, main terminal says app was built successfully, but an error is thrown instead of the metro terminal opening:
“launchPackager.command” can’t be opened because (null) is not allowed to open documents in Terminal.
The simulator just shows a white screen and can't be interacted with.
What I've tried:
manually opening node_modules/react-native/scripts/launchPackager.command
opens Metro terminal but is not connected to the app
warn No apps connected. Sending "reload" to all React Native apps failed. Make sure your app is running in the simulator or on a phone connected via USB.
info Reloading app...
giving Terminal full disk access (no change)
This happened to me after upgrading to macOS Ventura. I happen to use iTerm as my main terminal, not the built-in Terminal.app so the following fix only applies to that scenario:
Set iTerm as the Default Handler for *.command Files
Open node_modules/react-native/scripts/ in Finder (open node_modules/react-native/scripts/)
Right-Click on launchPackager.command and click Open With then choose Other...
In your Applications directory, select iTerm and click Always Open With
After this, you might need to run npm run ios again from this terminal window. However, from now on, Metro will open in a new iTerm tab instead of trying to open the command in a new Terminal window.
For me, this was the desired behaviour and it removed this warning.
Note In future, any *.command files will now open with iTerm instead of Terminal.
I encountered the same problem as you, I installed another terminal (iTerm2), then randomly found a .command file, and in the display introduction, changed the default opening method to iTerm2enter image description here
I'm having this issue after upgrading my MacOS to Ventura 13.1.
If you don't want to use iTerm as the accepted answer suggest, the workaround I found was to look for the launchPackager.command file inside node-modules/react-native/scripts/ and open this file manually every time you run your app for the first time (specifically when the error pop-up appears). This will open the terminal with metro running already.
I know that manually processes are not the best, but I don't want to use iTerm :)
Using Intel version of apps (Webstorm, Android Studio, other IDE etc...) fixed my problems. I encountered the same issue and thanks to Intel version of Webstorm and Xcode on Rosetta I can able to pod install and other operations.
Note: I'm using Intel version of Android Studio, WebStorm. Also Xcode uses Rosetta 2. No problem detected and everything works perfect. I can able to develop React-Native & Native Android & iOS and Flutter apps without problem. Before that I was using Silicon version of WebStorm and almost no function worked.
Config: MacBook Air, macOS Ventura 13.2 on Apple M1 processor.
For Most of the case you just have to delete node_modules and install modules again (npm i). This happens when project was copied from old mac which had node_modules folder created by the old user, or if the system thinks so
This happened to me after i configured my terminal for the look and feel - but with iterm2, oh my zsh, and powerlevel10k

Unable to launch app via appium capabilities but app launched successfully via 'xcrun simctl install booted install myApp.app'

Error message: ‘myApp.app’ cannot be opened because the developer cannot be verified.
I face above error when I install the myApp.app using Appium on my iOS simulator. However, when I install the same myApp.app using terminal command ‘xcrun simctl install booted install myApp.app’ then the app installed/launched perfectly fine.
Note: I am a tester hence I have not built the app using XCode and moving forward I will be getting the .app file only from the developer for testing.
Below are the details
Appium desktop client version : 1.15.1
macOS version : 10.15.2
XCode version: 11.3
I am using below appium desired capabilities for iOS
{
“platformName”: “iOS”,
“platformVersion”: “13.3”,
“deviceName”: “iPhone 8”,
“automationName”: “XCUITest”,
“app”: “/Users/harj/Desktop/myApp.app”,
“bundleId”: “com.abc.xyzApp”,
“commandTimeouts”: 60000,
“noReset”: false,
“autoGrantPermissions”: true,
“useNewWDA”: true,
“showXcodeLog”: true
}
Appium logs
There are many errors in the log but i found this one relevent
Original error: ‘idb’ has not been found in PATH. Is it installed? Read https://www.fbidb.io for more details
That would be great if someone faced the same problem and got a solution.
Happpy Testing
harj
I can able to launch the sample .app file on simulator with below versions.
I have resolved setup issue for simulator 13.4 version with xcode 11.4.
Simulator-: 13.4
xcode -: 11.4
mac os. -: 10.15.4
appium v -: 1.17.0
If you still face any issue then let me know. with appium logs and whole details.
Finally, the solution has been found.
Actually, the problem is with the macOS Catalina not with the Appium. The OS was preventing the .app to install on the simulator. There are two ways to solve this problem.
1) Degrade the gatekeeper(security) check on your mac.
2) Quarantine that specific app using below terminal command
xattr -dr com.apple.quarantine /yourAppPath/myApp.app
I recommended the option2 as it will keep your mac safe from attacks.

Attempt to update Xcode ends in endless wait

I am on MacBook Pro using High Sierra (10.13.4)
My installed version of Xcode is 8.2 (8C38) and I am trying to update to 9.3.1 but I end up in endless waiting.
it turns out that
(a) Newest XCode (9.3.1) required High Sierra MacOS
(b) And even you upgrade to HighSierra, you still have the same issue
So, I did following to resolve this
I updated my OS from El Capitan to High Sierra as I found out that in order to get latest XCode v. 9.3.1, you need High Sierra - this went smothless
Once updated to High Sierra, I went to app launcher and uninstalled XCode,
Next, I went to this link https://developer.apple.com/download/more/ and downloaded XCode 9.3.1 xip file
Once downloaded, unzip it using Archiver app
Once unzipped, just drag the XCode app to Applications folder
Start it to complete installation
Maybe #Apple should talk to their QA
Had the same problem. Deleted Xcode via Application menu. Reinstalled from App Store. Worked for me.

Xcode 8 : Unable to Accept License Agreement on OS X EL Capitan 10.11.6

I have downloaded Xcode 8 from AppStore, on clicking Xcode icon it is showing after clicking on Agree button it is asking username and password. On entering the username and password nothing is happening.
The problem i was facing "Xcode 8 : Unable to Accept License Agreement on OS X EL Capitan 10.11.6" is resolved.
Cause : It was blocked due to Symantec and Web Sense installed in my macbook
Resolution : Start your mackbook in Safe Mode (in safemode there is no Symantec and web sense installed) and then install Xcode 8.
To start macbook in safe mode try this : OS X El Capitan: Start up in safe mode

Install an IPA through USB?

After using the "iPhone Configuration Utility" program to install IPA applications to my iPhone on the go, I wondered how this process worked. Within a few Google searches, I found out about "MobileDevice.framework" and the "MobileDevice Library" connected to it. After reading an article of all the Known Functions in the library, I found one called "AMDeviceInstallApplication". I thought this would work once I saw install, but I'm currently perplexed on how to use it.
TL;DR I have IPA files and I want to make an Xcode program (for Mac) that installs the IPA's application to a connected iOS device when a button is pressed.
Also, don't worry about the application not being signed correctly. It is signed with a provisioning profile installed on devices [the application] will be used with.
If you're still interested in this problem I've written a blog entry on how to install apps on a connected iPad / iPhone without using Xcode or iTunes.
This method allows you to run a Terminal command to install an iPA file.
http://pervasivecode.blogspot.co.uk/2012/06/install-ios-app-ipa-file-without-xcode.html
I suppose you could bundle up the terminal commands in your application and use it that way?
I found a simple way to install iPa file to real iPhone or iPad:
Connect iPhone to Mac via USB and follow the below steps:
Steps to follow:
Open Xcode
Click on Window
Select Devices and Simulators
Drag and drop the IPA files into it
App got installed on the iPad