I am trying to install capybara-webkit gem on my macbook (sierra 10.12.6) but I still have some problems. I installed Xcode, gt, I tried almost every solution but I think I made it even worse :(
Now the error is "Could not resolve SDK Path for 'macosx'". Full message is on link down.
Can someone help me? :-/
full error message
Related
I'm testing the performance of my website with Lighthouse DevTool but I can't score 100% in Best Practices because keeps showing this as a problem:
Does anybody know what this means? How could I solve it?
You can find the specific errors in the "Issues" tab where the "Console" output is.
Also getting this, so you're not alone. Wondering if it was a recent Chrome bug I tried here - https://www.webpagetest.org/ and got the same useless error.
After a bit more digging, I found this closed issue on the lighthouse github repo.
https://github.com/GoogleChrome/lighthouse/issues/14233
So, it's been fixed, but only in version 10. Chrome 105 seems to be using lighthouse 9.6.2 and npm at the present time seems to install 9.6.7 (which has the same bug).
You can run the latest version by pulling the repo from github, building and running on the command line. See instructions here
https://github.com/GoogleChrome/lighthouse#develop
Note, the build doesn't work on an M1 mac, due to i386 specific build tools. I had to dig out my old macbook to get this working.
The problem is that when I run a flutter app after having installed a plugin (firebase_core in this case) I get an error:
An error occurred while processing the post-install hook of the
Podfile.
undefined local variable or method `continue' for
#<Pod::Podfile:0x00000001099e67b8 #defined_in_file=#Pathname:/Volumes/Coding-IT/Coding/Projects/flutter_37hours/ios/Podfile,
#internal_hash={},
#root_target_definitions=[#<Pod::Podfile::TargetDefinition
label=Pods>],
#current_target_definition=#<Pod::Podfile::TargetDefinition
label=Pods>, #post_install_callback=#<Proc:0x0000000109a07e40
/Volumes/Coding-IT/Coding/Projects/flutter_37hours/ios/Podfile:37>,
#installation_options=#<Pod::Installer::InstallationOptions:0x0000000109ab6eb8
#clean=true, #deduplicate_targets=true, #deterministic_uuids=true,
#integrate_targets=true, #lock_pod_sources=true,
#warn_for_multiple_pod_sources=true,
#warn_for_unused_master_specs_repo=true,
#share_schemes_for_development_pods=false,
#disable_input_output_paths=false, #preserve_pod_file_structure=false,
#generate_multiple_pod_projects=false,
#incremental_installation=false, #skip_pods_project_generation=false>>
continue if xcframework_file.start_with?(".") # Hidden file, possibly on external disk.
The problem appears to be with the continue word, but I don't know exactly why this is happening and how to solve the problem :(
I've tried reinstalling cocoapods multiple times, from homebrew and from rubygems, I tried flutter clean, I tried reinstalling ruby and changing versions. No luck. Hope someone can help me, thanks
I'm looking into this too. It seems to be related to this issue: https://github.com/flutter/flutter/issues/104118
But it's closed the fix seems to be merged with flutter master branch. Idk! Might need to wait for next flutter update.
edit - I just tried this on beta channel and pod install completed. So you can wait till it's on stable or switch channels to run iOS. Cheers!
I followed the install instructions for Flutter on OSX, and ended up with this error:
"Dart_NewStringFromUTF8 expects argument 'str' to be valid UTF-8."
Checking the github issues, this one seems to be closed but was not helpful in resolving. I have no weird characters in my file path.
I cannot find anything else on it that will resolve this error, nor do I know what/where to check to find out what is causing this. Anyone else ran into this issue on OSX?
I was able to fix this error by running flutter in verbose mode:
flutter doctor -v
This gave me clues on where the issue was on my machine. There was a directory with a non UTF-8 character and that tripped up the installation process. Renaming that directory solved the error.
Have you ever come across this error 'AmazonServiceExceptionUnmarshaller.h file not found' after installing the AWSiOSSDK 1.7.1 cocoapods?
I never faced it ever until today which unable to compile my project with it.
I have tried these potential solutions which were all failed unfortunately.
Ref: iOS - Build fails with CocoaPods cannot find header files
It would be really good if you give me a piece of advices.
Thank you very much
I solved this issue myself. All because of the version of the cocoapods.
If your cocoapods v 0.39.0, you will face the error.
PLEASE DO NOT UPDATE THE LATEST COCOAPODS!
If you have already updated it, try this command line as follows:
pod _0.38.2_ install
You can install pods with the old version (v 0.38.2) by force.
It should be fine.
Thank you!
I downloaded the latest version of CodeKit (trial version 2.0 (16828)). It starts fine on my Mac Mini, but as soon as I try to download a component using Bower, it fails with the error: "Bower Error / Bower could not determine which components are installed in this project. Make sure you're connected to the Internet and try again." Repeated attempts (either clicking "Retry" or clicking "OK" and trying to download the component again) continue to fail.
The app completes the "Downloading Bower component list" without error. The error occurs when it is "Scanning For Installed Components..."
I'm connected to the Internet just fine.
When I try to install a Bower component, it fails with this message:
Why am I getting these errors and how can I fix CodeKit?
Thank you!
Turns out that Bower continued to fail, which prevented CodeKit from working.
Tolga Akyuz's answer to Siddharth's problem was the fix - I had a ~/.cache file which was preventing Bower from adding files to ~/.cache/
When I renamed the ~/.cache file (e.g. to ~/.cache-orig) and created a ~/.cache/ directory, Bower began working properly - and so did CodeKit.
It turns out that this behavior can be caused by several things. Another user fixed it and shared this with me:
I installed xcode and still had issues. After a bit of research, I found a post that said installing the command line tools in Xcode might solve the problem. I did that and the problem is now solved.
From what I can see, there is a appears to be an issue with the $PATH getting messed up with systems that have been upgraded from Lion (and Snow Leopard) that did not ship with git. In the questions and answers listed on the page linked below, there were several terminal command options given, but I was unsure of which to choose so I went with the Xcode route.
https://apple.stackexchange.com/questions/18470/why-is-git-not-found-after-installing-os-x-lion
I had the same issue.
Check console messages (mac)
Delete faulty library. I had one.
Should be all good now.
good luck
If it's still relevant. In my case it was Google Maps AMD Loader Plugin. All fixed after removing it.
In my case the problem was with path to the project folder – it contains "!" symbol that makes bower crazy. To check is it Bower or CodeKit problem try to cd in terminal to your project folder and run "bower list".
zhaba$ bower list
bower EINVALID Name must be lowercase, can contain digits, dots, dashes, "#" or spaces
With corrected project folder path CodeKit works.
I had the same problem running CodeKit2 with El Capitan, and an old version of Xcode. Updating Xcode fixed the problem.