My black berry emulater no longer works. When every I run a program from eclipse, it comes up saying
JVM error 538
FS mltiplr errors
Scroll for availbe commands
Reset
When I click reset it does nothing, frezzes or exits. It does this no matter program I run
Did you try cleaning simulator? It is under BlackBerry menu in Eclipse. You can also try to delete .dmp files of your simulator manually.
Related
Running the iOS12 Simulator on xcode10 failed. but other versions of the Simulator were normal.
It may needs to set you command line tool.
Reset your simulator and install command line tool for Xcode 10.
Reset Simulator:
See Here: Xcode - install Command Line Tools
Its happens some time so, You have to do "Erase Reset Content and Settings" of simulator by below step.
-> Click on simulator
-> Go on "Hardware" in menu bar
-> Select "Erase Reset Content and Settings..."
Give some time after done it. Close Xcode and reopen it.
This symptom usually appears in two cases:
when the system app (eg: SpringBoard) crashes while setting up the debugging session.
because of buggy 3rd party kexts interfering with the normal operation of the system.
If you are seeing any background crashes of the system app around the time of the failure, that's the likely cause. Otherwise, you should check the output of kextstat | grep -v com.apple, remove any listed 3rd party kexts, reboot, and try again.
The problem is solved by moving the xcode file location under the application file, then restarting the xcode and running it.
Yesterday, I was working on my app and all was well. I had discovered two commands that would reliably start the remote debugger and run the iOS simulator. These two commands had been working reliably for about 48 hours, and I was so happy that I saved these commands in a text file on my desktop for easy access:
open "rndebugger://set-debugger-loc?host=localhost&port=8081"
react-native run-ios
Then I made a terrible mistake: I went to sleep. When I woke up, the commands no longer work. The first command launches the debugger, but the second command ("react-native run-ios") produces a variety of results, none helpful (see note below). At best, the simulator launches, but my app is a white screen.
After trying various things (listing processes to see if there is something to kill, rebooting the machine multiple times, etc) I decided to nuke my app and start over. So, I archived my app and created a new app with "create-react-native-app AwesomeProject" etc. I changed into the project directory and then almost ran "npm start" (as the docs suggest) but the terminal output suggested "yarn start" so I went with that. This gave me a QR code for an expo, but I still wanted the simulator on the screen. So I went back to the commands that were so reliable for about 48 hours:
open "rndebugger://set-debugger-loc?host=localhost&port=8081"
react-native run-ios
But they just don't work anymore. At best, I can get a simulator on the screen, but if I navigate to my app in the simulator, it is a white screen. I have tried "Erase all content and settings" in the Hardware menu for the simulator, quit the simulator, etc.
Will I ever be able to view the simulator on my screen again? Do I need to uninstall expo to get the on-screen simulator back? Should I just not sleep anymore? Will I ever reach I point where I can just wake up in the morning, quickly start the simulator and then be an app developer? Should I just give up on the simulator and adapt my workflow to use a physical device as the simulator?
Edit: To clarify, the variety of results include: simulator not appearing on the screen; simulator appearing and opening to the desktop of the iPhone, but when I navigate to the app and open it, it's a white screen; simulator appearing and app starting without my navigating to it, but it's a white screen.
Edit 2: Here is another data point. Just now I deleted my app again and created a new one with create-react-native-app. I then changed into the project directory and ran npm start. I then get a QR code and have confirmed I can open the app in my device using expo. And I see this error in my terminal, which might be unrelated to this issue:
2:31:11 PM: Error: './assets/icons/icon.png' could not be found, because './assets/icons' is not a subdirectory of any of the roots ('/Users/me/Apps/MyAwesomeApp')
2:31:11 PM: at /Users/me/Apps/MyAwesomeApp/node_modules/metro/src/Assets/index.js:192:11
2:31:11 PM: at Generator.next (<anonymous>)
2:31:11 PM: at step (/Users/me/Apps/MyAwesomeApp/node_modules/metro/src/Assets/index.js:329:347)
2:31:11 PM: at /Users/me/Apps/MyAwesomeApp/node_modules/metro/src/Assets/index.js:329:507
2:31:11 PM: at <anonymous>
So I have a working app and can test it with my device, but it would be nice to have the simulator on my monitor. However, "react-native run-ios" is not giving me that.
(Alas, this process below is not working reliably. It worked once. Then I tried to integrate opening the debugger into this process. A short while after posting this StackOverflow answer, I ran 'open "rndebugger://set-debugger-loc?host=localhost&port=8081"'. This seems to have broken the simulator, though the app still works in my device. I am now again trying to figure out how to get the simulator working. For a moment, the following seemed like the correct answer but it's no longer working -- now I get a "Runtime is not ready for debugging" red screen.)
I found a process that in this particular case gets the simulator working again (Update: It doesn't work. See my note at the top of this answer). I have expo on my Mac and on my devices, so these instructions assume you have the expo app:
In terminal, create an app with create-react-native-app. Do not sudo. No need to be root. Just a normal user.
Then, just like the react native docs say, change into the project directory and run 'npm start'. The terminal output suggests 'yarn start', but 'npm start' works for me.
When the expo QR code appears in the terminal output, use it. That is, install your app on a device by using the expo app to read the QR. Then, I think my next step was to open the expo app and then tap "Go to expo home" and then tap on my app to open it. And the app started up just fine.
Then, the real magic happens... I change into the project directory in a separate terminal tab and run "react-native run-ios". And then the simulator opens on my monitor and my app starts right up.
Thus, it appears that perhaps I had to run the app on my device first before I could open simulator on my Mac. Running the app on my device seems to get something unstuck.
Install the Chrome browser. Expo expects Chrome to be installed. With Chrome installed in Mac OS, a remote debugger will open in Chrome any time you run the simulator with react-native run-ios.
I keep getting the "The Simulator can't be launched because it is already in use." when trying to run my app, this only happens about 20% of the time but once so far the only way to get around it is to restart my Mac.
Tried the following but doesn't help:
Cleaning my build folder
Closing and re-opening xCode
Force close of simulator
I'm Using xCode 6 (beta 4)
Any Ideas for a solution that doesn't entail me restarting my Mac?
Thanks
"The Simulator can't be launched because it is already in use.”
This messege will be shown only if there is another xcode project that has launched simulator and hasnt stopped it yet, and u try to run the simulator from another xcode project.
Ideally stopping the simulator from the respective project(PS. not closing the application from the simulator, clicking the STOP button) would do it,
But if it still is working like that, then Closing the simulator, or resetting the simulator contents.
If that still dsnt work, then as a last resort i would ask u to reinstall Xcode, as if this problem keeps going on, then ur downloaded file might be buggy.
P.S if u opt to re-download n install xcode please keep backup.
Hope it solves it. Although i want your problem to be solved by step 2.
This normally just happens when running an app (project) on the simulator and then trying to run another app while the simulator is open (and normally is still within the first app you launched and it can't quit automatically). As long as you keep running the same app you shouldn't get this error and as soon as you run another app just make sure you've closed the simulator before or at least left the previous app with the home button.
Just Restart Your Mac , It Will Fixed
I had the same problem and fixed it without restarting. You just need to reset the content on ios simulator, exit xcode, and then to make sure that you've completely exited, right clicking on the xcode icon on your mac nav bar and click Quit. Open it back up and it should work.
As the title says, I'm having issues using LLDB. I've looked into this thread Xcode 4 hangs on attaching to (App name) when debugger is set to LLDB and followed the instructions given because I'm having exactly the same issue, and managed to debug by using GDB - it works flawlessly. Anyway, i'm working in a team and I'm the only one who's having this issue, so it's a bit annoying to switch back and forward from GDB to LLDB every time i commit changes so the workaround doesn't get synchronized in the remote repository.
I've checked the compiler, and it's set to LLVM 4.2. In fact, the app compiles perfectly and gets installed in the simulator (i can execute it once I kill and restart Xcode). I would try to reinstall Xcode, but it's a mess since it's a big-sized package and I have a limit on my internet usage, it would take a long while. Does anyone know what's happening here? Is it possible that LLGB is bundled outside XCode, even if I failed to locate it on the system?
Any insight would be appreciated. I can keep the workaround going, it's just that it's a bit annoying given my personal circumstances :-)
EDIT: More details about what I mean by 'hung'. I start with Xcode open, and simulator closed (it doesn't even appear on the Dock). I click 'Run', the simulator is launched successfully, and the application shows the Splash Screen. Then xcode shows the message: "Attaching to ". And now it's hung. You can close the simulator, and xcode is still attaching. Both the Run and Stop buttons stop working. You can try to exit the application by right-clicking on the dock, you get an alert message, and from this point you can't even type code: XCode is fully hung. The only choice here is to kill XCode by using Cmd+Alt+Esc.
This sounds like it could be the problem some folks were seeing in Why does the LLDB Debugger constantly fail to attach? where they'd modified their /etc/hosts file so when Xcode tried to connect to debugserver via "localhost", the connection was never set up.
When Xcode hangs, try switching to Simulator by clicking on its Dock icon. Don't use Cmd+Tab.
Upgrading to XCode 4.6.2 fixed this issue for me
How to Run two instance of BlackBerry simulator in windows eclipse?
The documentation regarding developing with BlackBerry Messenger indicates that you can run two simulators at once, at least with the simulators that come bundled with the BBM SDK.
You cannot. If you try, you will get an error message saying only one simulator can run at a time.
What you need to do is:
Install the blackberry eclipse plugins twice and make two
workspace of each eclipse.
Run the two simulators in each eclipse and error like "could not
open port 19780 and it is use by another program....." will pop
out in one of your simulator.
So made the changes in pin,
data-port values in .bat files, rimpublic.property files inside
MDS and fledge-settings.conf in one of your simulator... but this
changes will not be reflected on your eclipse.
So what you need to do is, when you click the debug configuration from your
eclipse, you will see the simulator option there. So, click the simulator and change the PIN value, whatever you have made the changes in .bat files.. and just after that in the simulator you will again find the option of network, there unselect the disable registration button...once all this changes is made click apply and restart your eclipse... this will surely solved your problem