I have an app with some TextInput on a screen. I had to do changes on a component which doesn't affect the layout of this screen nor those TextInput in any ways. For what I can say, everything worked fine until then but now if I'm taping a TextInput the keyboard appears but it does not respond at all (like not at all). What I can't figure out is why this happens only on my real Android device when using expo start. On a virtual Android device it works just fine. It also works perfectly on both if I'm using expo start --no-dev --minify. Reverting the project back doesn't resolve the issue. Any clues on where or what I should investigate?
Silly me, looks like the expo performance monitor was causing all the trouble. Disabling it resolved the issue. Would be nice if someone knowing the why would take the time to educate me.
Related
I am using the Sfml library on C4droid which has official sfml support. Everything works just fine, I can run the program normally and it renders graphics normally. But after i like minimize the app for a second and then open it back up again, for some reason it doesn't render anything at all, not even the window. Although everything else in the program runs normally like the sound,touch input, calculations etc. And I know it's not because C4droid is doing something wrong because every other graphics library i tried doesn't have that problem. Only sfml has it. I even tried it with Cxxdroid and I get the same problem.
I ran the sample programs so it's not a coding error. I tried using the the onlostfocus event to reload the files after it loses focus, I tried using only sfml shapes and no textures. But still the same thing happened. But after I tried to create a new window onlostfocus by using window.create(), It actually did render the new window even after minimizing and reopening but it only did that and didn't render/draw anything.
Is there a reason why it is happening and is there a way to fix it?
I FOUND THE SOLUTION!
I went to the sfml discord server and a really NICE person helped me out. All you need to do is just window.setActive(false) on lost focus and window.setActive(true) on gained focus AND IT WORKS FLAWLESSLY!!!
My Android emulator crashes whenever I press keys on the pc keyboard or hit the emulator side buttons. the only part that works is the emulator mobile screen. This doesn't happen to just one device but to all emulators I use. This is really annoying cause whenever I press any key on the keyboard while the emulator screen is active it will instantly crash. But keystrokes won't crush it when text input is active on the emulator screen. The operating system I use is ubuntu but Windows fix is also useful.
I need help from someone who has managed to solve this problem before.
I'm pretty sure I got this error before too. Whenever I pressed a button, the emulator would just say "Saving State..." and just closes. The only solution I found to fix this was to delete the emulator and create a new one. It's not the most effective solution, but I couldn't find any other solutions.
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 ?
I have tested my application using ionic-serve and everything run normally.
But, when i tried it using device, the application will first run the splash screen (which is not run when using ionic serve) and nothing happen, only white screen.
Can somebody please help me with this situation?
I have no idea about what happen.
The white screen issue often occurs on devices and not in the browser when you are injecting something into a module that kicks off your app. Try to figure out which one, and remove it (if it's not being used) or update it.
First thing to do is to check for errors in the log. To see them, type the address chrome://inspect/#devices in chrome, and click on your app. You'll need to make sure your device has usb debugging turned on.
I try to run an embedded web in Android, but it crashes when using Android 4.3 (Nexus 4). I run the app and the first webview appears correctly, but when I touch the textbox and the keyboard appears, the view gets frozen just on the top part of the keyboard (where the text predictor is located in case it's active).
This problem only appeared when using 4.3, not with the previous versions.
I've been trying to fix the bug as it says in this issue, but the solutions they give don't resolve my case: https://code.google.com/p/android/issues/detail?id=42518&q=webview&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
I would love if somebody have been through this problem, because we don't know what to do to fix it...
After more than one year without trying the app, it is working now. The device now is running Android Lollipop, so I guess that probably the WebView has some improvement that avoids the bug.