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 ?
The Issue that i'm facing is that when i install the application that i have made in android studio the system UI crashes no matter which mobile i install it to.The other thing is that if i press the recent tabs button it'll always crash.even then when i try uninstalling that application my Application Crashes and i'm not able to uninstall the application. can anyone help me with what should i do to stop facing these issues bcos i cant test my application not as the system UI keeps crashing.
UPDATE : issues is solved as the problem was that the icon that i was using for the logo was very big in size due to which the application would crash.
App Crash on Android Tablet and when ever tried to open it again it open a blank black screen there after. This is happening with android debug build.I have tried to replicate the issue on simulator and it didn't happen. Please let me know if any clues about this issue. Is it something related to inefficient memory usage or something else. Is there any tool I can use to narrow down this issue. This is not happening on IOS devices and even Android Phones.
I've noticed that every time I run a cordova app using cordova run android, it seems like the menu button is being pressed, the context menu on another currently open app pops up.
It doesn't bother me but I was just curious if anyone else has noticed this peculiar behaviour...
Yes, this is normal. I can observe the same behaviour while developing on an android device.
I've created a sample application (just a textview, nothing else), and I noticed a bug.
After installing it from the SDCard, it displays the "Application installed" screen, with the done and open buttons.
If I click the open button, a strange thing occurs:
Whenever I put the application in background and reopen it from the application icon, it doesn't reopen it, it creates a new instance.
I can confirm that it is creating a new instance, because after putting it on background and reopening a few times, when I click the back button, it opens the previous instance, instead of returning to the home screen.
Now the strange thing is that it only happens after installing from the SDCard and clicking on the open button.
If I click the done button (or installing via ADB) and open the application via icon, it doesn't happen.
Also, if I click the open button (and the bug occurs), after the application is ended for the first time, the bug doesn't occurs anymore.
I've tested it in different devices and in different Android versions (GB, HC and ICS), and the bug is reproducing in them all.
Does someone know if this is an known issue from Android and if so, does someone have an official reference that I can refer?
Thanks in advance
Yep, it is a nasty, well-known Android bug that has been around since the very beginning. See the following:
Android issue 26658
Android issue 2373
Android app acts differently installed from adb vs sdcard