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 ?
Related
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.
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.
sadly I am facing problem with One Signal and my react native application. I don't know why but somehow my push notifications aren't working anymore.. But only on iOS.. I have had the same problem with Android too but Android is working again. So, that means that the problem cannot really be the react native code cause it is working on Android.
However, when I receive a notification on my iOS device the screen remains white and the application doesn't crash. This is actually not good cause that means I don't get any crash log.. And you cannot debug iOS devices on a MacBook cause Apple has deactivated to receive push notifications on the iPhone emulator..
So, I don't really know what to do.. All I did was replacing the icons and the splash screen. On both, Android and iOS. Also confusing is, the application gets compiled and build without any problems on XCode..
I have read some issues on GitHub already but none of them are working.. What I am really wondering about is, why it is working on my Android device but not on my iOS device..
I already tried to solve the problem by deleting the node_modules folder and create it again by npm install. However, this didn't fix the problem. I also runned pod install again and checked the OneSignal documentation to double check if everything is correctly installed.. And yes, everything is correctly installed..
You guys have any idea on what to do and how to solve the problem?
After I tap on the notification the app launches and then remains on a white screen..
If the app is running in background and I tap on the push notification everything works fine!
But when I am inside the app and I receive a push notification, the app "crashes" and keeps remaining on the white screen. As well when the app is completely closed and I tap on the push notification.. The app "crashes" and keeps remaining on the white screen also...
You guys can help me?
Kind regards and Thank You!
If you don't have an IOS-Device, but only an Emulator it will become really hard to debug this.
You can give it a try with output some Test-Strings with respones-values at important points inside of your app (e.g. function for recieving Notification, for sending notification ... and so on.)
But if you need more help you have to provide more Information. What Library do you use for Firebase-Notifications (fcm, rnfirebase.io or other)... how did you implement it...
If the app is running in background and I tap on the push notification
everything works fine!
But when I am inside the app and I receive a push notification, the
app "crashes" and keeps remaining on the white screen.
Yes, here you have the Point where to start with your debugging. If receiving notifications in Background work, you're issue might be found on the Event-Handler which listen for foreground notifications.
Did you have a clean Code-Structure, where you use try & catch for all your api-based request (notification-methods)? Then it shouldn't be hard to found the issue by echo some catched errors
I have an Android app with a corresponding Widget. It works perfectly in the past before 2017Nov. However, After my update to the Android studio, Gradle, and build tools. The app always build with an app that cause "Problem loading widget"
.
To make sure I am right I get back my code version before 2017Nov, and recompile. Problem still here. To solve this problem, my only way is to reboot the device. After reboot the device, the widget loads normally. My question:
What kind of special system calls the Android device will trigger when restart the device?
More information: Actually I have done one more test. While my widget is live and no problem is shown after reboot, I uninstall it, reinstall it. Then problem loading widget immediately appear. After that reboot, problem gone.
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.