I'm used to debugging my React Native (0.63.2) app using Safari's dev tools. I got an M1 Mac Mini last week and have since been unable to get the console or source tabs to show anything from the iOS simulator. Not sure if this is related to the new machine, or if I missed a setting. Any ideas?
I usually do Develop > Simulator > JSContents from Safari, and everything would show up fine. I can get logs in the terminal, but Safari's devtools are much easier to manage.
Installing and using the "Safari Technology Preview" from https://developer.apple.com/safari/download/ worked for me.
I'm trying to get my react-native project to run on an android emulator while on a Mac operating system. It worked fine on my windows.
On my Mac, I go to terminal and type react-native run-android and I get the error message:
$ react-native run-android
Scanning 616 folders for symlinks in /Users/John/Documents/myreactnativeproject/node_modules (17ms)
Starting JS server...
Building and installing the app on the device (cd android && ./gradlew installDebug)...
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html
I type adb devices and I see
List of devices attached
emulator-5554 unauthorized
I go into the settings of my android emulator, I go to Settings Build Number to tap it several times to enable Developer options. In developer options, I enabled USB debugging, disabled Verify apps over USB, and left everything else as default. I shut down my android studio and emulator, restarted it. But still, the same issues mentioned above.
What am I doing wrong?
EDIT
I just connected my android phone to my Mac. When I run adb devices, I see this result
List of devices attached
YLEDU16B18004313 device
But when I run react-native run-android, I get the same error as above. So maybe there is something wrong with my react-native set up instead?
EDIT 2
I was able to deploy the app to my android phone by adding these extra steps
chmod 755 android/gradlew
For some reason, when I type echo $ANDROID_HOME into the terminal, I get the result /Users/John/Library/Android/sdk. But if I add the echo $ANDROID_HOME line to my android/gradlew file, it echoes nothing. And when I run the react-native run-android command, the compiler complains that ANDROID_HOME is not defined. So I have to type export ANDROID_HOME=/Users/John/Library/Android/sdk again, then running the react-native run-android command works and deploys it to my phone.
However, my emulator still doesn't work. The new error message I get is that Skipping device 'emulator-5554' (emulator-5554): Device is UNAUTHORIZED,.
But at least I have a temporary solution, and to debug with my phone.
EDIT 3
I got rid of the emulator 5554 unauthorized error by going into my Android Virtual Devices and deleting the virtual device. Then I re-installed it. And now my adb devices shows emulator 5554 device. And I am not able to deploy the app to my emulator.
In my case, Create a Virtual Device with Google APIs Image, not Google Play Image worked for me.
The problem occurs the only emulator that runs on Android Pie others don't.
In Android Studio
Open an Android Virtual Device Manager.
Create a new Virtual Device.
Select any Hardware you want.
Select any System Image which the Target is "(Google APIs)" not "(Google Play)" (If you don't found. Try to look at "x86 Images" tab or "Other Images" tab)
Done!
Android emulators have by default "Usb Debugging" in settings. You just need to wipe the data of the emulator. Do the following steps. It will work :---
Close the emulator and run the command adb kill-server in the command prompt. If adb is not set in you path then you might run this command from directory where adb is present.
Click on Wipe Data option from avd Actions menu.
Now run the emulator. It should work.
create new Virtual Device, and make sure you choose Google API's.
run the new device!. this should work
In my case, following steps worked
Wipe data from avd manager
Cold boot now
I managed to authenticate the adb on a Pixel 2, Android 9.0 (Google Play), API 28, x86_64 virtual device (Intel HAXM). The problem should be related to the Extended Controls (the 3 dots bottom icon menu, when the virtual device is booted), the Google Play menu, that is checking the version of the Google Play services. When adb is not 'unauthorized', this page is displaying the correct version, and the Update button opens inside the phone the Play Store with the Play Services app, so you can update it.
The steps I took to be able to authenticate are:
Make sure the USB debugging is turned ON in Dev setting
Revoke the USB debugging authorizations
Make sure the Extended Controls > Settings > Advanced > Open GL options are set to the: 'Desktop native OpenGL' and 'Renderer maximum (up to OpenGL ES 3.1)', so the emulator interface, animations, etc, are fast!
Power off the emulator
In 'Your Virtual Devices' in Android Studio, click the down arrow in Actions > Select 'Cold Boot Now'
When the device boot, you have to be fast, the dialog to remember and accept the USB connection will show and disappear for like less than 1 second (again I guess related to some automation scripts kicking, idn).
If you manage to click the 'remember' and 'ok' checkbox and button before the dialog disappears, you are done. Else you have to Power Off and Cold Boot again.
After that, don't wipe your emulator, else you'll have to do that insane race clicking again!
I run adb kill-server and adb devices.
the device will back again.
for Emulator, the default settings is debug enabled
Creating an emulator with graphics set to "Software - GLES 2.0" worked for me (Nexus 6 image).
I was initially using a Nexus 5X image which didn't allow me to select the graphics option.
NOTE: I went through the steps mentioned in EDIT 2 and EDIT 3 by the OP before doing this.
This can happen if USB debugging is not enabled on the emulator device.
Go to the emulated device, enable the Developer options and enable USB debugging.
I had to create a new emulator with Google Api. Wiping data didn't work for me.
2022 answer
What a shame of thread: so many "answers", comments and upvotes and none worked. Nobody simply mentioned that the "adb unauthorized" is caused by the adb keys stored in ~/.android/adbkey and ~/.android/adbkey.pub After deleting and recreating them, the problem was solved.
Credit: Android Emulator Unauthorized
I got my mac system to deploy a react-native build to my physical phone by following Edit 2 in the question.
I got my mac system to deploy a react-native build to my emulator by following Edit 3 in the question.
I think the issue was generally caused by moving my project from a Windows dev area to Mac dev area. Then probably a combination of different issues happened that cause builds to fail for each situation.
Deleting emulator and creating it again helped me on Ubuntu
I solved Problem
add ANDROID_SDK_HOME to environment variable
ANDROID_SDK_HOME = D:\sdk
and unplug device
and use new cmd
I have new installed Xcode 8.3 with iOS 10.3.
My application ran on iOS as expected and suddenly Xcode fails to run application on device with error:
Could not launch "My app" process launch failed: unspecified
It runs on Simulators and on other device mini-pad (10.2)
I also have this problem when run in iOS 10.3.1 with xcode 8.3.2
Restart device, It will work well
I tried plugging out-in the cable of iOS - doesn't help
I restarted iOS device and Xcode - everything works as expected
(hope it will help to someone)
Plugged out the device cable.
delete App.
restart device.
Delete Xcode Derive Data
Quit and launch Xcode again.
Build and run successfully.
I had similar issue. Tried below steps :
Quit Xcode (cmd + Q)
Clean project (cmd + shift +k)
Delete Derived data (cmd + comma)
But these didn’t worked. Instead restarting device worked!
Running the app on the simulator shows: "Unable to boot the iOS simulator". I'm on Xcode 6.0.1.
I tried everything: resetting the simulator; selecting the Xcode 6.0.1 command line tools; restarting the Mac. The problem is still present.
Try this. In Xcode menu: Open Developer Tool > iOS Simulator. When it opens, use the menu to go to Hardware > Device > Manage Devices.... In that list, delete the non-working simulators and re-add them.
Also make sure that the Downloads section of Xcode preferences is up to date.
Do you have DYLD_INSERT_LIBRARIES set? If so, this is a dupe of:
Unable to boot iOS 8 Simulator
Check /etc/launchd.conf
I have just upgraded my xcode version to 5.0. After running application 2-3 times it's giving me error like this "iOS Simulator failed to install the application". This is working fine in old xcode. When I reset the simulator it works fine, but this is irritating again and again.
Can anybody tell me what is the real issue? How can i resolve it.
Did you find new solution for this thing?
Try manually launch the iOS Simulator and from the "iOS Simulator" menu, click "Reset content and settings", then close and rebuild your app. It worked for me.
i got the same problem but solved by following way....
launch the iOS Simulator
Go and click "iOS Simulator" Menu
click "Reset content and settings"
close simulator and rebuild your app.
Above screen shot is showing the way how you can do this...
I think this works for you...!!!
I just used CMD+SHFT+K and quit the simutor and then run again and it's working, no need to reset simulator or delete an applicaiton.I'm not sure but some time it will work.
Just delete the application from the simulator and build it again.
Or try to use a device with different iOS version.