i'm new to react native and native apps in general and i'm using windows 10.
i have downloaded java and android studio and configured path variables.
i have node installed already and used it to get react-native-cli.
i have initialized a project and troubleshooted all errors.
after running run-android command i get the output of a successful build and it seems like everything should work but the emulator is not responding. i tried API 23 and API 24. does anyone know whats the problem might be?
Related
Trying to create a new app on react-native. 'react-native start' command gives no error. But I'm not able to see my app on the emulator. Can anyone help me in figuring out the problem. I'm new to react-native.
Are you using a Macbook or Windows? For Windows, you will have to use an Android emulator, thus you will need to download Android Studio, and the Android SDK.
For Mac, you will use the IOS emulator, you will need to download Expo in that case.
Also you could try using the create-react-native-app instead. I built a project with 3 other buddies in two weeks, we found that it had the most reliable boilerplate and is really good for beginning with react-native.
*** Edit:
*** Big caveat with create-react-native-app is that it won't matter what OS your computer has. If you have an apple phone, you just run "npm run ios" then scan the QR code with expo. If you have an Android phone like I had...you will run into a few issues where you need to set the phone to USB debugging mode in the developer's settings, download the USB debugging driver for your phone's model, ensure both your phone and computer are on the same wifi network, install expo, and finally be able to run "npm run android".
I was the only one on my team developing with an Android phone, so if you need advice on that, feel free to ask.
Some extra information about create-react-native-app is that it allows you to code for both Android and IOS phones by using the same project folder, rather than having to adjust settings for one platform at a time.
That has it's pros and cons for sure and there will be little differences in how one platform functions over the other...so my recommendation is to build for one platform at a time, focusing on whichever one you are testing on.
Since you're using Ubuntu
Getting started with create-react-native-app:
https://github.com/react-community/create-react-native-app
Starting Guide for Setting up the Emulator or App Environment on phone:
https://facebook.github.io/react-native/docs/getting-started.html
I am trying to load the SDK for Vuzix through the SDK manager in Android Studio but for some reason it will not display the downloads in 'SDK platforms' and 'SDK tools'.
In the 'SDK update sites' tab next to the Vuzix link I added there is a red exclamation point that displays " cvc-elt.1.a cannot find the declaration of element 'sdk: sdk-addon' " when hovered over.
I am new to SDK's and have no idea what to do for this error. I've downloaded the android SDK's and sources for 26,25,24, and 23 thinking it could help but the error still shows up.
I still don't know what the error means but I solved it by connecting to my hotspot instead of my work network.
So my guess is it was a firewall issue or something, if anyone else has this error.
This means that the parser does not know the namespace. I tried it on Win7 and android studio 2.3.3 with the same result.
I tried it without the namespace or running android studio with oracle sdk. Both failed.
At the moment I try to run it on a virtual linux machine. Android Studio 2.3.3 will parse the addon xml file and download the files.
On Win7 I installed them manually, but they were not really integrated into to system and I stucked when I wanted to use the barcode SDK. maybe I am able some day to add simply this jar lib -
On a first look using linux seems to be the solution. But than I run into problems with the case sensitve file system. The vuzix SDK seems to need a linux system on a case insensitve file system.
*facepalm* and I am quite sure that i will fail at all. On linux a simple GUI compiles only against API 26 without errors.
We have a Xamarin.Forms app for iOS and Android that we have in the stores for some months now. We develop with VS 2017. For testing the iOS-version, we use TestFlight.
Everything worked pretty well, until mid-april when we wanted to test a new release via TestFlight:
We installed the iOS-App on our test devices via TestFlight, and now on our test devices the app closes down right after the splash screen without generating a crash report (we use HockeyApp).
The app works fine though on the iOS-simulator and when being published directly on a device (iPad) via VS.
We found out that the problem is the update of Xamarin.Forms from version 2.3.3.180 to version 2.3.4.231 or later.
We would like to use latest version of Xamarin.Forms. Does anyone have the same issue and did you find a solution?
We just found the solution for this problem:
We use a custom font for our app and changed the font of the navigation bar in the AppDelegate.FinishedLaunching method by using UINavigationBar.Appearance.SetTitleTextAttributes.
This caused the iOS version of our app to crash when distributing via TestFlight. We removed the code to change the font and now we can publish the app again.
I am creating a purely server side nodejs app in visual studio and the majority of times I go to debug it, it does not start running my javascript.
I see "Debugger listening on port xxxx" and nothing else.
Opening and closing the project solves it and have had some luck manually ending the VSHub.exe process (maybe coincidental) but I don't want to have to do this everytime I debug.
Anyone seeing this or got any ideas?
This is a known issue with the node js tools extension.
The fix was included in dev build v1.1.Dev-9.17.2015 which is available from here until it is included in an official release.
I had the same problem with the Community version, deleting the project, reinstalling VS2015, then recreating the project seems to have fixed it.
Mysterious.
Hoping someone can help. I've been through every forum, the online help, every youtube, and every example to find an answer. This either means it's incredibly nuanced or incredibly simple and I'm just missing something that seems to work for everyone.
Nodeclipse/chromedevtools failed to connect to Standalone V8 VM
( Check Help (F1) and Support http://www.nodeclipse.org/#support )
. Info:
connect timed out
I get the above error when I use nodeclipse to debug a node app using the right-click menu on the project. DEBUG AS -> NODE APPLICATION.
When I RUN AS -> NODE APPLICATION, it launches just fine. But when I run with debug-as, I get that error and the debug info looks like.. (or not.. I can't post images... but it terminates the V8 VM entry)
I've installed JDK 8, the most recent NodeJS, the express packages, enide studio from nodeclipse.org, and followed the instructions to build a starter app (new - express project), then attempted to debug that app with debug-as->node application.
I can successfully debug a node instance (my actual project) that I start from the command line, and it lets me step through the virtual project files, etc.. but I was looking for the "all in one" nature where I am debugging the same files I'm editing and can launch/test it all from within eclipse.
Win 7, 64bit
JDK 1.8.0_11 64bit
node 0.10.29 64bit
nodeclipse/enide studio 2014-011-20140228-win64
I've tried it with JDK1.7 as well (64 bit).
Any and all help would be appreciated.
Regards,
Zig
While the issue happened before it is hard to reproduce on other machines.
More stats is needed.
http://www.nodeclipse.org/#support gives links to Online Help (the same as built-in by F1)
in particular
https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.help/contents/run.md
and https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.help/contents/debug.md
Have you tried to
to run node --debug-brk app.js first, and then again in Eclipse/Enide Studio ? #107
I've had some luck getting around this error by:
Right clicking in the server and selecting run as -> node application
Navigating in Firefox to the address where my server is listening
Stopping the server in the console
Right clicking in the server and selecting debug as -> node application
I also created a new perspective called "visualstudio" and do no switch perspectives between development and debug (though I doubt perspectives have much to do with the issue)
Using this approach, I get an interesting anamoly where the debugger breaks on line 1 when the server starts, and I then have to click resume. However, after resuming, execution only stops when a request hits a breakpoint.
You have to run the command to debug the node.js file:
node --debug-brk yourfilename.js (this is not working now)
node --inspect-brk yourfilename.js