I am attempting to make my own app with React Native, however it appears as though I'm working harder to get Expo to work more than I am trying to actually debug the app itself. I have tried with LAN, Tunnel, and Local but none of them seems to work. I will get it on some days and it will work fine.. for about 5 minutes and then it will time out or lose connection. Some days though it will just continue to try and load but will never actually pull up the app. I suspect this is because I am using my hotel wifi as well as a vpn (for security on a public network of course). I am wondering if there are any alternatives to expo that I might be able to use because this problem is starting to become very frustrating. Thanks!
You should be able to start Expo in offline mode so that your internet shouldn't be an issue. If you're using yarn the command would be yarn start --offline. You may also need to select Local once Expo launches.
Source: https://github.com/expo/expo-cli/issues/101
Related
I've made a bot/app in visual studio code and Node JS and it runs fine, but i have other projects I need to relaunch as well while keeping the current one running. I remember having this problem years ago called pm2, thought it was pretty useful, but as i recall the bug problem was while it could relache the app if it crashed so it stayed up 24/7 i didn't have acess to the console log which i use to track the topic that trigers my app, the user name who triggered it and the response. Anyone familiar with PM2 or another program that would retain the console for each running app?
Edit: found some info via
https://pm2.keymetrics.io/docs/usage/quick-start/
theres even a web app you can set up to run your app
https://app.pm2.io/
but as of yet i haven't found a way to easily monitor the console.log output
so near as i can tell the best way to monitor the console long va the web app is with
console.log(`log`);
As this works flawlessly with my discord js bot, however my reddit bot doesnt seem to use it so it may be API specific on what can pass/use Console.log
It all started when I tried to use the hot reload for storybook, which worked fine on my Macbook, but for whatever reason didn't work on my Windows machine.
I always got a request to __webpack_hmr which would be in the pending-state für about 10 seconds after which it got cancelled and then this cycle would start again.
Since I was running into the same problem with the very basic example from the webpack-hot-middleware GitHub I could rule out storybook.
After a bit of playing around with the example I finally figured out that when using --host=[::1] to start the "server" the hot reload actually started to work. But no luck using anything else like --host=localhost or --host=127.0.0.1.
But I'm still wondering why does the IPv6 host work, but no other configuration? Has anyone run in the same problem before? Why is this problem windows specific and is there anything I can change about my setup?
I'm taking an online course and created an app for a previous project and ran it on localhost:8000. I did use service workers if that matters. Now I'm working on a new app, also on localhost:8000 but it is still showing the previous app. If I go to the page in firefox, I see the app I'm working on but I need to see it in chrome. I never opened my previous app before in firefox, which is probably why I can see the new one.
Any idea what's happening here and how to fix it?
Thanks,
Michael
You should probably check your terminals if you have left your previous server running, and change the port to view your current project.
This problem has been driving me crazy which pushed me to make an account here hoping someone can help. My app has been deployed for about 5-6 months and was working fine until I checked it about a week ago. The app (both local and AWS deployed) works if I have the server running with babel-node server.js in terminal. This is because it keeps trying to use localhost to get the games when it is supposed to use mongodb through heroku. I tried clearing the heroku cache, editing various parts of the code to no avail and I am stuck. I've only been coding for 2 years so I am sure someone here with more experience could figure this out, at least I am hoping. It is an older project with older dependencies but it should still be working. The front-end is hosted on AWS and the backend through Heroku. I'm also using the Filestack API but I don't believe the error is from there.
I think the error is in games.js in the sagas folder or maybe GamesListManager.jsx in the components folder. Any help or suggestions would be greatly appreciated. Thank you.
P.S. If you are looking at the github repo and my commits, make sure to go back to the last Jan 11 commit as that was the last working version (and the version deployed to AWS).
http://www.oldschoolgames.com.s3-website-us-west-2.amazonaws.com/
https://github.com/shahramg92/Videogame-library-react/tree/2327f503e204381745eacc996a2ccbdb09fac970
snippet of possible problem (in src/sagas/games.js)
const API_URL = process.env.API_URL || 'http://localhost:8081';
I think it keeps trying to access local host (when I inspect it keeps saying failed get request from local host).
Basically, when I make mistake somewhere and the app crashes, no matter what I do, it stays crashed. Deleting last changes, restarting the server, nothing... So, I have to create a new project, copy everything to a new project, and it works.
Help please, I have no idea what's going on.
Running the latest version of Meteor on Linux Mint 18.2.
When you get the message "Your app is crashing" in the browser, I think it has given up, and you need to refresh the brower. In fact, refreshing the browser is sometimes necessary anyway.
Meteor detects changes to files pretty well, but sometimes struggles with new, deleted or moved files, and you may need to restart meteor and refresh the browser. You shouldn't need to copy to a new project.