On mac OS Catalina, for Fastlane, I am seeing an error whenever I try to run any Fastlane command.
"nokogiri.bundle" can't be opened because its integrity cannot be
verified
I researched and found that the mac os gatekeeper was blocking this as it treats it as an unidentified developer.
A similar issue was reported on Fastlane GitHub issues for ruby.
https://github.com/fastlane/fastlane/issues/15186
To allow execution
Goto System Preferences -> Security & Privacy and agree to run the
app
Related
I'm running MacOS Sierra, and this is the first time I've seen '/etc/ssl/certs' in my system. It doesn't exist in Yosemite or earlier. But that directory is EMPTY, so I have no clue what to supply for the certificate to use Gmail. Until I get that, I can't supply 'smtp_tls_CAfile' in main.cf so 'smtpd_use_tls=yes' works. All my sent mail is being rejected by this:
530 5.7.0 Must issue a STARTTLS command first
I've heard that and also based on threads, MacOS Sierra Postfix is broken. It seems a bug on this version because after upgrading to MacOS High Sierra without any configuration changes, it worked perfectly.
Additionally, I've run some tests with machines. The result is the security patched for Spectre and Meltdown is causing this issue on my Mac OS Sierra. Without this patch, Postfix is working well.
I have a sandboxed Mac application that will no longer launch fully on Sierra. It seems as though it's unable to read the app bundle directories.
There is a folder located at ~/library/Containers/com.company.app/Data/Gallery/. On fresh installs the app is unable to read from this directory with Sierra, where on OS versions previous to Sierra it could. Current installs updating the app also have access to the directory.
This is related to an entitlement that we're missing but after trying the following it's still not working. When we disable sandboxing the app launches and works as expected.
We've tried these by adding them manually to the entitlements.plist;
com.apple.security.temporary-exception.files.home-relative-path.read-write
com.apple.security.temporary-exception.files.absolute-path.read-write
com.apple.security.temporary-exception.shared-preference.read-write
Any help would be greatly appreciated. This issue is currently blocking any future app updates. Unfortunately a recent update somehow snuck through review processes with this bug so we're in hot water...
Thanks a lot!
I successfully submitted my app [ version 1.0 ] to iTunesConnect for review. And they have rejected it because I have added an extra App Sandbox feature. So I solved that thing and tried to archive my project in new build number.
Also I have selected my Code Signing Identity 3rd Party Mac Developer Application, And came back to Project Settings -> General, now I could see that the Signing switched to None and Team automatically changed to None. So I have changed that to My Team Name and Signing into Mac App Store. Now I have went back to Project Settings -> Build Settings, There the code signing identity has different identity selected [ Two Mac Developer & One 3rd Party Mac Developer ].
So what happens is that whenever I change something the opposite happen in other place. Basically I am unable to archive my project cause of code signing issue.
If I try to code sign using Mac Developer Identity, it shows me something that I never seen before.
Something like error: A cryptographic verification failure has occurred.
*** error: Couldn't codesign /Users/Alvin/Library/Developer/Xcode/DerivedData/MyApp-bjtynsmrmxhrfffdvpfwxeanbgkb/Build/Intermediates/ArchiveIntermediates/MyApp/InstallationBuildProductsLocation/Applications/MyApp.app/Contents/Frameworks/libswiftCore.dylib: codesign failed with exit code 1
So how will I solve this problem? Thanks in advance.
By the way, I am using Xcode 7.3.1 in macOS Sierra. Is that can be a problem? No right?
It seems there may be code signing issues with macOS Sierra. You can follow the issue here.
I would recommend reverting back to El Cap and only installing an early beta of a new Mac OS on a machine used for testing the OS, not one you are doing active development on.
[update 7/6/2016]
Some developers are reporting this fixed with macOS Sierra Beta 2 and Xcode 8 Beta 2, but I have not yet comfirmed on my spare Mac if this fixes the problem.
Also, some developers have reported that resetting the Keychain fixes is. In the Keychain Access app , go to "Preferences..." and click "Reset My Default Keychain".
I use
rvictl -s 36621ee66871bfa671997c023a1b9197ef6a4b37
to set up an RVI for my iPhone, but it just return
Starting device 36621ee66871bfa671997c023a1b9197ef6a4b37 [FAILED]
Try ensuring you don't have a hanging rvictl process with:
rvictl -x 36621ee66871bfa671997c023a1b9197ef6a4b37
I ran into the same issue on macOS Big Sur 11.5.2 with Xcode 13.2.1 when trying to start an interface for iPhone 12 SW Version 15.2.
After restarting my MacBook twice I was asked to change my Security & Privacy settings by unlocking the settings lock and giving Xcode the requested permissions.
I'm not sure if this really is the cause but for me it worked. It is also possible that I have been prompted to grant the permissions before but did not see it.
After upgrading to OS X 10.6 (Snow Leopard) and iPhone SDK 3.1 (with Xcode 3.2), Xcode's shared workgroup builds (distributed) can't seem to find or access other computers in our office.
Distributed builds worked perfectly in OS X 10.5 with iPhone SDK 3.0.
All the computers that have upgraded are now listed with a status of Unreachable. Even my own computer, artanis, is listed as Unreachable!
I've already tried all of the suggestions listed in Troubleshooting Distributed Network Builds. And none of us have the OS X firewall enabled.
Any suggestions?
Here's a screenshot:
Xcode Preferences Screenshot http://img170.imageshack.us/img170/3972/screenshot20090917at104.png
The solution seems to be to run Xcode in "32-bit" mode - you set this in the "Get Info" dialog in the Finder.
You must re-install Xcode using the version on the Snow Leopard DVD. The iPhone SDK must be re-installed afterwards.
Edit: I just noticed that Apple started distributing Xcode 3.2 with the iPhone 3.1 SDK. I would recommend you to attempt a full uninstall of the developer tools, as described in the SDK release notes (see developer.apple.com), and then to re-install it. You should also check that each computer have a unique name set in system preferences>>sharing. As a last resort, I'd check that Snow Leopard was booted in 32-bit mode (it does by default), and (just for the test) try to boot Snow Leopard in 64-bit mode (hold the 6 and 4 keys while booting).
Edit 2: Check this thread, it seems related. Maybe you should try to enable Xgrid in sharing preferences?
I had a problem installing it now it works since it needed for the xcode and ipphone sdk the firewall disabled to install, I think that fix my problem where it did not want to install the files strange bug I guess, with firewall on , the installer fails to install, and I am still in 64bit mode