Safari extension window says "No Extension". Can't add any extension as well. I am running macOS Mojave 10.14.5 (no beta).
Following did not help : Disable/Enable Extensions from Develop menu, restarting safari, restarting mac, removing ~/Library/Preferences/com.apple.Safari.SandboxBroker.plist
This might have happened after I installed a profile (.pkg file) to receive beta OS update. But I never installed the beta.
How do I add extensions to Safari ? Any help ?
Related
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
I'd like to force Safari to mark one of my domains as tracker with new ITP 2.0.
I followed the guide here https://webkit.org/blog/8387/itp-debug-mode-in-safari-technology-preview-62/
Since the new Technology Preview version (66) doesn't have ITP Debug mode I've used normal Safari 12.0 on macOS Mojave. After enabling ITP Debug mode and restaring Safari I don't see anything in logs as the guide suggest nor does setting
defaults write com.apple.SafariTechnologyPreview ResourceLoadStatisticsManualPrevalentResource example.com
have any effect (even with Safari instead of SafariTechnologyPreview). Do I need to change any other Safari or OS settings?
I've managed to get Safari Technology Preview 63 download link (https://secure-appldnld.apple.com/STP/091-99601-20180815-01EC2FD2-85EB-11E8-AB5B-AEA972136C40/SafariTechnologyPreview.dmg) via InternetArchive, ITP Debug mode works there.
Thank you Jakob. That helped me. To clarify your link, that version is only for OSX Mojave. Build 62 for High Sierra is available here: https://secure-appldnld.apple.com/STP/091-95878-20180801-01EC2FD2-85EB-11E8-AB5B-AEA972136C40/SafariTechnologyPreview.dmg
On newer version of Safari Technology Preview, or inside Safari 13.1+, you should use these updated steps for enabling debug, because the labels have changed: https://webkit.org/blog/9521/intelligent-tracking-prevention-2-3/
It says Catalina, but they also work for Mojave.
protractor version : 5.0.1
safari version : 11
Mac version : 10.13
selenium version : 3.0.1
Error message: safaridriver could not launch because it is not configured
I have enabled the safari driver using the command --enable but still it is not launching the browser
Any possible solutions for the issue ?
A lot of times, it's because the developer option to allow remote automation isn't clicked. In safari, you can access this by clicking 'preferences' -> advanced. At the bottom it says 'show Developer Menu in Menu Bar.' Click that. Then in the newly appeared develop tab click on 'Allow Remote Automate' towards the bottom of the list. If this doesn't run it, post your code and we can take a more thorough look.
I just upgraded safari to version 9.0.3, one of my parners in another city reproduced an error on my website using responsive desing mode and iOS 9.1 iPhone user agent in a MacBook (OSX 10.9.5).
They were explaining me how to reproduce the issue by using the "Enter responsive design mode" in the develop tab but no matter what I do, that specific option never shows up. I already disabled all extensions and deleted my preferences (not sure if this helps). I tried the option + command + R shortcut but it doesn't do anything neither. I already tried reseting safari and restarted several times.
Where did this feature go?
Edit: added screenshot:
Edit: 2nd screenshot:
According to Apple's Documentation, you have to be running OS X 10.11 El Capitan or above in order for Enter Responsive Mode.
With OS X El Capitan, Safari brings new tools and capabilities that let you create a better surfing experience with the Safari web browser.
Source: https://support.apple.com/kb/PH21491?locale=en_US
As you are running OS X 10.9 Mavericks, you are not able to enable it.
Thus, you need to upgrade to OS X 10.11 El Capitan in order to enable Responsive Mode.
I have problem as following. I use a Titanium Studio, build: 3.1.1.201306112235 with SDK 3.1.1 GA (on Windows 7). When I try to run example app as "Mobile Web Preview in Browser", then I saw mobile app in my Firefox (version 21.0) but any actions associated with 'clicks' don't work. Furthermore when I try run the same app in Chrome I see the same behaviour. Only in Internet Explorer app works properly (version 10). Do you have idea why apps from Titanium don't work properly? If you would like to get some more logs just ask.
EDIT: I provide remote access, and reopen page by Firefox in the same version on my colleague's laptop. Then in here browser everything works well. So i have question which settings, on my browser can "freezing" titanium application. Javascript is running, so I don't have idea, what is bad in my configuration.
This sounds like you are making web service calls to a remote host, which violates the same-origin-policy built into recent versions of chrome.
Try opening up chrome with this policy disabled:
chrome.exe --disable-web-security