I've started developing a react-native app using Expo and running it in my Android phone. Things worked OK at first but then suddenly:
Every time I introduced a syntax error on my code, my phone would not display the compiling errors (they used to appear as white text on a red background) but instead it would show an uninformative error screen with a blue background.
My phone stopped responding to the shake gesture in order to access the dev menu. (I wonder who thought that shaking was a good idea as opposed to a more conventional menu...)
Live recompiling stopped working.
Even when refreshing manually, changes to my code sometimes won't be applied. It looks like the expo app is working with an old, cached version of my code.
Expo is indeed running in production mode. Any pointers?
Since you mentioned your project is running in production mode you must change it to development mode, you can do this by clicking the toggle button on expo-cli's interface.
Alternatively if you're using Expo CLI just press p while your project is running to toggle between modes.
You can read more about Dev/production modes here.
Related
I have an Android app made with Delphi 10.4.2, it works fine.
Now, I have downloaded Delphi 11 trial version, and tried to run the app on Windows and Android. It won't start, it just crashes.
So, I tried creating a new test app to see what the problem is. I found that as soon as I change TMultiView.ControlType from Styled to Platform (important because of a TWebBrowser used in the app), it crashes. In fact, it doesn't even start, it hangs until I end the process via the Task Manager. If I change it back to Styled then it works, but because of the TWebBrowser it doesn't cover the app like it should, the TWebBrowser stays on top like in old versions of Delphi.
Any ideas why this is happening, and how to fix it?
We are facing a very weird issue with our Flutter Mobile app (Android version only). As displayed in the screenshot, the bottom part is getting cut, and the app loads only in the 3/4th part of the screen only.
This is coming in the released Playstore version only. In debug mode, this never happened on an emulator or real device. Also, this occurrence is very random and irrespective of the device model. If I close the app and re-run it works fine most of the time.
Flutter Version - 2.5.1
I think it's regarding the error.
When we run the app in debug mode the flutter shows a red box for error.
When we release the app with that error then that part is shown with a white box. So I think you are getting some errors on that part.
To check something wrong in release mode connect your real device with a computer/laptop then in your vscode terminal write the following command
flutter logs
then launch your app you will see your app all logs with errors.
If you don't understand post a comment on this answer I will reply.
I wanted to share a very annoying problem I have with Expo React-Native. It does not break the app or something but it is just annoying to work with.
I am using Expo and I am using the Android Studio Emulator. Expo is installed on a Virtuall Device and its working properly, however I have this problem for a longer time I think since ReactNative 0.61(or 0.60) when they implemented "Fast Refresh". There are time "Fast Refresh" does work right but sometimes when changing a small thing u get an Error thats something like:
Attempted to assign to readonly property.
When you reload the app so the error goes away expo shows a white screen with an endless blue spinner... It's just annoying to quit the node server, close the app, open devops in a browser and bring everything back up everytime.
Has anybody experienced the same behavior or knows a fix for this ?
We have a (rather complicated) Qt application, with port to Android. It worked quite OK - until we started trying it on Android Pie.
Sometimes, either after start, or after return from background, application visually freezes - however, logging shows that UI thread is alive, it responds to taps, widgets receive paintEvent()'s and process them. But nothing changes on screen.
Hardware buttons like 'Back' also work - application is able to show 'Are you sure to exit?" message box and it works properly.
Also, you you try to go ot home screen and back to app - most of the time it unfreezes.
Actually, this behavior started on Android 8, but was resolve with a dirty hack - doing hide/show for main widget upon receiving applicationStateChange(Active). But it stopped working on Android 9.
I am completely out of ideas what could we do to produce such behavior, and how to fix that...
After a long and rather tedious debugging we finally narrowed it to a problem in Qt itself.
I've reported a bug: https://bugreports.qt.io/browse/QTBUG-76142
However, I don't know whether it was fixed in newer releases, since we stopped development of Android apps for now.
This is not an actual solution, but shares some ideas. I used QT 6.3 and the same hang/freeze problem occurred in qt android app (arm64-v8a / Qt widgets) after returning from background or after phone auto off when app is opened and after return to phone on. Another consequence is that after sending the app to background, I can't use Google chrome properly (I only tested this app, not other apps). What happened is that it's very slow and scrolling in Chrome doesn't work as usual.
I suppressed this problem with this trick (not a solution): i.e., before sending the QT app to the background, I triggered it to show a message box (from clicking a button) and let message box open. Now the Google Chrome app worked normally. And after dragging the QT app to the front and giving OK to the message box, I was able to use the application as usual. No hang/freeze problem.
Also I read an article from a link (https://lists.qt-project.org/pipermail/interest/2014-November/014218.html) : That is, we can able to modify the QtActivity.java (which can communicate to the QT app) and use the on pause and on resume event. So what I thought is that, If I trigger the app to show Qt message box from this "on pause" event, and automatically close the same in the "on resume" event this hang/freeze can be handled.
But I didn't try above (modify QtActivity.java) because now I switched to QT 6.4 and hang/freeze problem is not present in this version.
I'm coming from Visual studio and C# and am new to Android (and eclipse) so quite ignorant of basic functionality.
I've written a short app and ran it under the emulator. No problems.
Now I've made some changes and want to test them. In VS I'd stop the application debug run before making code changes, and after the code changes run again.
I can't find the 'stop' debug button in eclipse. How do I run my app after I've made changes?
What you can do is press the [Escape] key on your keyboard or the 'Back' button within the Emulator to close your app then rebuild and run it in Eclipse, which should bring it up as active in the Emulator.
You can just run it again and the code changes will apply.
But else you'll find it under the Debug-window (Window->Show View->Debug) and there is a "terminate" button in the top right corner of your screen.
You might need to close the app inside the emulator though..
There is deference between just running the application and debugging, you can pres play in ellipse and that will run the app but what you can also do is to switch the perspective in debug view (to switch go to the right top corner, and change from java to debug perspective)
in debug mode you can also set break points, just like in visual studio the only difference here is you must change perspective