hope you all doing good,
so my problem is that I can't run metasploit on my iPhone and it's kind of frustrating since I'm sure I followed the installation steps carefully.
When I type "ruby msfconsole" it says that Metasploit requires the bundler gem to be intalled. So I searched for it and found that "gem install bundles" should fix it, but It didn't!
And here's a screenshot of the whole process:
Thanks in advance!
i know this issu i had it my self but when jou see the error it says easy sead that the ruby code doesent get the encryption that happand most of the time on iphone i think that you downloaded ruby from cydia but the ruby 1.9.3 version from cydia is broken what jou can do is go to cydia and install the metasploit pakkage from there after install go back in the terminal and go to whear it is i guase usr or var jou will find it and start it from the metasploit map it will work but it is not the latest version because the version 4 wont work on iphone!!!!!!
3 does.
i hope that this works and jou cant fix ruby that bug dit i dont fix :(
sorry for bad english.
Related
I'm not sure how, but I managed to install version 1.8.4 of cocoapods. However, I can't update it. I need to update it because the pods for the firebase google sign in require FirebaseAnalytics, and Firebase Analytics requires cocoapods to be 1.10.0. Whenever I try to update it, either by simply sudo gem install cocoapods or sudo gem update cocoapods, I get the following error:
The compiler failed to generate an executable file. (RuntimeError) You have to install development tools first.
This is odd because I do in fact have xcode developer tools installed.
And here are the pods (one of which requires FirebaseAnalytics)
Also see the error message:
This question is similar to several others--I'm asking a new question because the answers to those questions didn't help me and the questions were fairly old, so I doubt I'll get any help there.
I greatly appreciate your help. This problem alone is stopping me from using Firebase's google sign in in my application.
EDIT:
After I re-installed cocoapods with brew I checked my pod version, only to find that it was still 1.8.4. I then ran brew upgrade cocoapods and everything seemingly looked up to date. But I checked the version once more and am still seeing 1.8.4. What is going on here?
EDIT 2: bundle result
I was able to successfully (seemingly) install bundle, but I'm getting errors when I try to use bundle to install / update cocoapods.
EDIT 3: Solution Found?
I tried upgrading cocoapods again with brew, and for some reason it worked this time--even though last time I tried upgrading cocoapods with brew it didn't work. (Did bundle help?) I still have yet to see if this solves my original problem, but cocoapods is now version 1.11.2, the newest version. Thanks for all the help!
I think you are using the latest Xcode. just make sure your system cocoa pods up to date with the latest version. so just try this command in your terminal sudo gem install cocoapods and again try to install.
because firebase requirements in their website
You can also try - install swift package instead of pods it will also work
So I tried implementing Facebook Login and followed all the steps accordingly. After having errors with FBSDKcorekit/FBSDKcorekit.h' file not found, I decided to pivot over to working on other components.
Lo' and behold, I have this error giving me trouble now. I followed along with this video: https://www.youtube.com/watch?v=rAXVKapP5cM&t=458s where I used the react-native install react-native-fbsdk and react-native link react-native-fbsdk commands in my terminal.
If it helps, I'm getting the following compile error in my terminal:
The following build commands failed:
CompileC /Users/someUser/desiredProject/ios/build/Build/Intermediates/RCTFBSDK.build/Debug-iphonesimulator/RCTFBSDK.build/Objects-normal/x86_64/RCTFBSDKGraphRequestManager.o RCTFBSDK/core/RCTFBSDKGraphRequestManager.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
I'm not sure if it was the tinkering around with the react-native-fbsdk or making links to it that caused this error. Note my project was working before I was trying to implement Facebook Login and using the link command.
What's going on here?
Thanks in advance for your time and patience.
edit: Also I did not implement any of the Facebook login code yet since I couldn't get a successful build on Xcode.
#kdizzle Make sure you have the right packager running in the terminal, sometimes you may have a packager associated with another react native project running, this happens because when you stop running an xcode RN project, it doesn't stop the packager in the terminal, and when you start/open another RN project in xcode, it simply checks if a packager is running, doesn't check if it's associated with the current project. So make sure you stop all of the packager instances in the terminal and then open the RN project again.
This may happen when upgrading a project to a newer version of react-native. To fix it,
Stop your packager.
Quit your iOS/android simulator.
Reinstall your modules: rm -rf node_modules && npm install
Restart your packager and simulator, e.g. react-native run-ios
I had this issue and it happened when I changed Hardware within the simulator. To fix it I had to kill the packager and run 'react-native run-ios' again. It didn't happen all the time but when it did this fixed it for me!
Another use is in a Brownfield App. Check your iOS and/or Android react-native versions. If they don't match exactly you will see this error screen too.
For example: I had a react native instance running 0.45.1 while Android had 0.45.0 installed. The solution for me was to make sure everything was running the same version.
None of the above answers have worked for me, so I researched the 'react-native' options a little and ended up:
Deleting the iOS and android folders from the app directory altogether
Running 'react-native eject'
Re-running 'react-native run-ios'
After that the iPhone emulator seemed to have no problem with the app.
This problem would appear when React Native libraries in ios project can not found.
I happend to meet this problem when i update my react-native version from 0.42 to 0.44, and cause that a file named RCTConvert+Map disappear in 0.44, so i update my pod.
command: pod update
hello guys i am having problems wile trying to install cocoapods in el captian i just updated yesterday and cant install the cocoapods due to this error
terminal results
im kinda new to mac and xcode and everything i have already looked at all the answers that might have helped like
Cannot install cocoa pods after uninstalling, results in error
and entered the codes bud didnt get any result on it so if u could explain the issue in a simple way that would be great thanks
hey after some research and asking from some friends this is what they offered me
Sounds like there is some SSL issue in your RubyGems installation, maybe this can help. Another option is to use the OS X app as installation method instead: https://github.com/CocoaPods/CocoaPods-app/releases/tag/0.39.0
i used the app and it solved my problem
thanks anyways
I'm trying to start eclipse but it crashes after the splash screen and before workspace selection.
This is version: eclipse-java-indigo-SR2-macosx-cocoa-x86_64 on Mac OSX 10.6.8
Launching the eclipse application or executing the alias from a shell ./eclipse (or Eclipse.app/Contents/MacOS/eclipse) results in a segfault.
$ ./eclipse
Invalid memory access of location 0x10 rip=0x7fff84ea3164
Segmentation fault
However, it runs successfully as the super user
$ sudo ./eclipse
Password:
This is fine for now, but running eclipse under sudo does not seem like a good idea.
To make this stranger still, this installation of eclipse worked fine a few months ago and I can't remember changing anything relevant.
Any ideas?
Thanks
Before taking the more drastic step of re-installing Java on Mac OS X [not always so simple :( .. ], I just reinstalled Eclipse and ADT - and it worked fine after that.
In my case, I got this error trying to start Eclipse
Segmentation fault: 11
.. it appeared in my Eclipse ADT setup after I updated the Android SDK for Google Play Services, and then tried to run Installation of update from "Check For Updates". Restarting the computer did not help.
I would try re-installing Java. The Apple installer might thwart you, but this can help get past it.
I'd suggest getting the Java Developer package from Apple, as it includes Javadoc and source for the core libraries.
I started out developing on C. I know what gcc is, libgcc, and so on . I've done Windows/.NET development for years, and now I am playing with an iphone.
I understand that it's possible to compile apps on the iphone itself.
Wanted to start with a hello,world. I have openssh on the phone, and am connected from the Windows machine via putty.exe.
using Cydia to install GCC, it tells me "Cannot Comply".
The post I cited above says I may need fake-libgcc. Why? What's fake about it, and why do I need it? If this is a pre-req for gcc, why doesn't the GCC package in Cydia install it automatically?
I just barely got this figured out myself, and since Google doesn't seem to have any recent and sufficient information, I'll go ahead and explain what I've found out even though this question is rather old.
The quick of it is this, gcc needs to see libgcc installed. I installed fake-gcc from here and it let me install gcc, and it appears to be running just fine, however, it still needs the headers. Here is a walkthrough that should help get the appropriate header files so you can get it to work.
As for why this all is, this is what I've been able to gather from searching through Google for a little while. Let me just start by saying, this is pretty much pure speculation, and if someone points me to a more correct reference, I'll gladly update this.
It appears that up through version 2.0 of the toolchain, libgcc was installable through Cydia to provide the basic libraries for gcc. However, since version 3.0, these libraries are (maybe?) now built in by default, so installing libgcc again through Cydia broke things. But as gcc has it as a dependency, it can't be installed until it sees libgcc somewhere.
That's where fake-libgcc comes in. It registers itself as that package, but doesn't really do anything besides that.