I used to open the react native dev tools on my android emulator (AVD) using ctrl+M.
But lately it stopped working.
I have tried to change the android keyset but it didn't help.
I put a breakpoint inside the java code and I noticed that I didn't get key pressed event for ctrl+M or other control keys (I got for other keys).
I am using UBUNTU 14.0.4, android SDK manager 25.1.6, react native 0.24.1.
Please help.
Thanks
Related
I'm using Visual Studio 2017 to build and deploy a NativeActivity to my Android device. It builds and deploys with no issues, but I cannot set breakpoints.
Before running, I can add a breakpoint to a line (the first line of android_main() for example) and the little red circle shows up on the left of that line in the IDE as you'd expect.
But after installing and running the app, the breakpoint doesn't trigger because the red circle has turned white - it's saying there are no debug symbols.
I've verified I'm building the Debug version and have verified the APK file is bigger and has the debug symbols by using Android Studio.
At this point it appears to me that Visual Studio itself is confused and somehow doesn't recognize the debug symbols.
I've added "-g" to the C++ options manually, and have added the Gradle line packagingOptions.doNotStrip '**.so' as well. But still this problem persists.
What would cause this behavior in Visual Studio and how can I fix it?
The Xamarin debugger can only debug managed (i.e. C#) code. Breakpoints only work with the Xamarin debugger if the project being debugged is a managed project. They don't work if the project is a native app or native library.
So you have to make NativeActivity c++ app be attached to a Xamarin Managed App(Acttach to Process）to get what you want.
1) create a c# xamarin android app and then input that xamarin managed apk file into the NativeActivity c++ app's Properties-->Debugging-->Package To Launch
2) start Xamarin c# app first and then make the Xamarin debugger active. While the managed app is still running or being debugged, right-click on the native library project and select Debug --> Attach to Android process.
Here is an example provided by Richard Walters and he provided the detailed info.
I've installed Android Studio to run a React Native application on an android emulator.
I've followed the instructions from the react native website under Windows / Android.
Now when I try to run the simulator I'm getting the error below. I've searched for the error but no useful results found.
I've reinstalled Android Studio but to no success. Any idea on how to fix this?
I was getting same error while launching Android Emulator.
My c drive Users folder was hidden and Ready Only. I unchecked both Read Only and Hidden chekboxes.
Then it started working for me.
Similar to #Supriya Bhosale's answer to unhide the folder - specifically the Android/Sdk folder.
I moved my Android/Sdk to D drive because of C space constraint. In my Windows 10 desktop it was working even with the Android\Sdk folder hidden. But not in Windows 11. So unhiding it fixed this error for me on Windows 11 using Dolphin version of Android Studio.
I have been trying to debug the native android code that is invoked through platform channel in flutter and the debugging is only in the flutter side. The execution doesn't hit the breakpoint in the native android. The application is working as expected but the debugging doesn't. I am using Android studio. Can some one please tell me how to debug the native android code ?
Breakpoints are working fine for me when using Android Studio at project/android/, on both emulator and physical device. And remember to Debug instead of Run (^D instead of ^R). Note, it did not work when opening the project from project/.
I don't think making a new android project to write the Native code for a flutter app is a good option (vivek's suggestion). There are many Flutter specific considerations you need to make on the native side, it is not just an Android app.
If you navigate to MainActivity.kt or MainActivity.java in the android studio then you can see "Open for Editing in Android Studio" on the top right.
click on that and it will open you a new window where you can easily write native code.
Well, better if you can write whole code in a new android project and test there then use that code to make flutter plugin. I think this will be faster than to edit in flutter project.
let me know what others think.
The answer given by #Marcos Boaventura to follow this blog helped fix the issue. https://medium.com/flutterpub/flutter-app-couldnt-find-libflutter-so-c95ad81cbccd
After fixing the gradle the debug is successful. Thank you #Marcos Boaventura
I had a similar problem. Debugging native code on an emulator worked, while debugging on a physical device (Zebra TC25, Android 7.1) crashed with a Fatal signal 11 (SIGSEGV). Switching from the Flutter beta channel to the Flutter stable channel fixed it for me.
I am running my React Native app in Visual Studio Emulator for Android. Can someone tell me how can i debug my js code ? In Android studio simulator we have options to remote debug. But from Visual studio Emulator how can i debug..Thanks in Advance.
If you have chrome installed, then you can use the chrome debugger to debug your js code.
First
Mac: command + M
Window: control + M
Then click debug js remotely; It will open a tab in chrome, then right click and select inspect, switch to the console tab. Any statement you console will appear there.
There are two ways you can debug your code.
First one : Using visual studio debug menu.
Press ctrl+shift+D to open up debug menu and select Attach to Packager or select 4th item on the left in visual studio.
This allows you to set break points and debug code as you see in Android Studio.
Second one : Using React Native Debugger
I can't make an App Works in a real device using Mono for Android 4.2.7
Im using an Xperia X10a with Android 2.3.3
When I tried to open it in a real device it close; "The application has stopped unexpectedly. Please try again."
Im am using Visual Studio 2012 Ultimate, in Project -> Properties; Configuration "Release", Use Shared Runtime (no).
Please help me, thanks for your time.
before you install it, you must create a serial key and then publish it.
for More:Xamarin Documents