I have used Headless from React Native.
I have setup all configuration for it and run my test script as showed in offical site tutorial.
It works when my app is working in foreground.
Whenever I close or switch another app, my background script also stop working.
Is there any option to allow code to work in background after closing app?
Related
Getting strange issue for ionic 5 app,
Application works fine till it is in foreground.
Once application minimize and again maximize it is unresponsive , freeze on scroll , page routing are slow.
I have checked in logcat logs , it shows Skip 100 frames, Main thread doing too much work.
but app is just come back to foreground nothing changed.
also shows error activityResumeTrigger: not whiteListed /mainactivity.
I am using ionic 5.4.16
Hope someone answer it,
Forget to mention , i have implemented AWS App SYnc, is that is reason of main thread doing lots of work when app resume.
Tried to do a bit of research without finding a result, however:
I am connecting to my development server over the same wifi network and using hot reloading to update react native Application on physical device, however I can’t seem to find a way to display the console output like I normally would through the temrinal. Normally I would build my app with physical cable and display log through the console and use react-native log-android.
What’s the way to show console logging when connecting wirelessly?
TIA.
have you tried the option Debug Js remotely, which opens a new tab in the browser and from there if you press f12 and go to developer tools ,in the console tab there you can view all the console log statements. And to start Debug Js remotely, you shake the phone and the option will be displayed. I hope it helps.
I'm working on a React Native app, testing in an android emulator. I've used the standalone React Native Debugger app as well as the debugger that opens in Chrome. In the Chrome window, the Network tab shows no activity, so that's no help. In the standalone debugger, the same is true until you right-click and choose Enable Network Inspect. The problem I'm having is that after I enable network inspecting in the debugger, all network requests fail - the inspector shows their status going from Pending to Canceled after a few seconds. I can see in my server logs that no requests are coming in. It's like debugger itself is somehow blocking the requests.
I've set up adb to run as root. When I run react-native run-android the output includes Running adb -s emulator-5554 reverse tcp:8081 tcp:8081, so I think things are starting up fine. The network requests from the app (login etc.) work fine (a typical URL would be http://10.0.2.2:2080/api/LoginScreenController/GetIdentityStatus), until I choose "enable network inspect" in the debugger, at which point all network requests fail as described above.
Any suggestions would be appreciated.
I know that I'm too late but perhaps it will save time for somebody.
During the update of the react-native, I did update the version of the react-native-reanimated from v1 => v2, and after it, I faced the same behavior.
Version 2 requires to enable Hermes engine if it won't be enabled then all the requests will be in pending status
A bit of context (I have been stuck on this for a few days now):
The first screen on my Ionic 4 app is the login page. Once I logged in successfully, everything works fine. Then, when I log out & log back in, the app just hangs. There is no error showing up on the console. So, my question here is, how can I debug to find out what is causing the app to hang half way using it?
*It hangs in browser mode and when it is running on android.
In order to debug your app step by step I recommend using chrome developer tools.
First you will have access to your source code, therefore you can put breakpoints at any position you want.
You can open this window by inspecting your page and selecting the source tap.
To locate the problem you should have an idea about Ionic Page Life Cycle
,
If none of the above works you still have the possibility to console log the code that you want to verify, also the template can cause such an issue if you have for example an infinite *ngFor or something that prevent the template from loading.
I have started working in Sencha Touch 2.1.1. I would like to know the following:
What is the best work flow for a Sencha Touch app during development? Testing in Chrome may not give the actual mobile view. How can I test my app on Windows during development?
xtype 'label' is not getting resized when I change the browser size.
After changing the code each time I come to Chrome and refresh, but it takes a few seconds to load the app. Is there any quicker way?
Host you app using WAMP or some we server and open it on you mobile
device is you are using same WiFi.
please attach screen shots
Its not an Egyptian magic, it will take few seconds pal...