Logcat not showing logs when a testing device becomes idle for some time. After each 10-15 min, logcat stops logging logs from the device and I have to do each time disable and enable ADB integration to logcat to work again. How to solve this so that logcat logs continuously?
Related
I have a server/client react app that should be logging in the window from where I launched the app. The client logging in showing in Chrome's dev tools, but the terminal window from where I launched the server app is not showing any output, at least not anymore. I was running Visual Studio Code with the debugger and I was asked a permission to allow debugging, I clicked yes and now no output to the terminal window from which I started the server How can I undo this?
I had several processes running even though the terminal window was not running. I had to kill the processes to allow the console logs to come through.
Not sure where to go with this one as I am not sure if it is code related or something else. I have a working React Native app that works great on the simulator and also on the device when connected to the wifi or plugged into the Mac.
Now I have noticed that when I remove the device and place it on 4G/3G the app does not load and hangs on the loading screen. It may take a number of re-opens of the app before I can get it to run once. Funny thing is that at the minute the app only has the UI built so there are no calls to remote servers etc that may be causing it to hang.
Any ideas?
For iOs, in Xcode you can go Product > Scheme > Edit Scheme... > Run & set the Build Configuration to Release. Then run it on your device & it will be a release build that won't try to connect to your packager, but won't have the sometimes useful developer options at your disposal.
Once I finished building my app for iOS on the codename website, I tried downloading it onto my iPhone but whenever I click install an error message pops up saying
"Cannot connect to codename-one.appspot.com"
Make sure your device has a valid internet connection and that the browser can reach https://codename-one.appspot.com/
If you are behind a firewall you might need to configure your device to use a VPN or go around said firewall.
All developers in my team are experiencing the same issue with the new app engine dev server, which hard crashes when debugging via eclipse. The server runs perfectly in "Run Mode", but in "Debug Mode", it starts up fine, but as soon as you hit it with a request, it hard crashes with nothing logged in the console.
Anyone else getting this issue? And any tips on fixing it?
I recently started building applications on Google App Engine. I use an Eclipse plugin to start and stop the server and deploy applications to run on Google App Engine.
I had created a new project and tried to stop and start it as suggested in the tutorials and in Stack Overflow. My old project is still running and hitting the data source successfully. I even removed the old projects from my Eclipse workspace and tried a fresh deploy of the new project with no luck.
How do I stop the server (the RED dot in my Eclipse has no effect)? Is uninstalling the App Engine the only solution?
When you launch the server, a new Java process is started. You can find and kill it independently of Eclipse.
I too ran into this problem and found the solution at Stop or restart a previously started Google App Engine local server in Eclipse
Just in case the link breaks, the key steps are:
In Eclipse, find the Eclipse Console view (looks like below).
Select the arrow next to the small computer and find the server's name
Select the red square to stop the server
Go to http://localhost:8888 to see if the page is still showing (it shouldn't be)
If you are visiting something like http://yourAppId.appspot.com and the server is still running, that's because it's still deployed on App Engine, not locally. In this case, go to Google Developer's Console and stop the service there
The server can be stopped by clicking red square icon in the console window. If this icon is missing or disabled, you may see wrong console window. You must select the javaw console using the drop-down button on the far right of the console window.
Go to Run/Debug Configurations -> Select your project configuration -> Common tab -> Uncheck "Launch in background"
Now, when you terminate the server on Server's console, it will stops the server.