currently i'm developing an App with the Framework Ionic2 / Cordova.
The application is ready for the beta test and i uploaded it to the Google Play Store. In the release everything works realy good.
Today i tried to change some stuff in the code and recognized a problem, when i run the application from my pc on my phone.
After the splash screen there is a white screen showing up for about 30s !
Ich checked the device with the debugger and after the app is installed the "Device is ready" fires after 3s. For the whole rest of the 30s nothing is happening. After that the app shows up and everything is working like before.
I have already tried to build the app with --prod --release but it makes no difference.
So my first choice was to reset my project to an older git commit to fix the problem, but now in every! commit the screen is white for about 30s. I can go back like 10 commits and it still there.
I was thinking about an problem with the cordova plugins or something like that and that's why the problem occurs in every version now.
Could that be possible or someone of you has advice for me?
/edit:
Intriguingly when i want to debug the app and run it with
ionic run android --livereload --consolelogs
it shows no error, the white screen after splash is still there, but it only lasts like 5 seconds
Related
I have a flutter app I am developing. When I run the app in debug mode it works really well. However when i export the APK version there's a very weird thing that happens. When I tap on the app to open it, sometimes it loads well with the splash screen and everything displays correctly.
Other times when I tap on the app icon it loads without the splash screen and the whole app is a mess.
The screenshots above, the first image is the result when the splash screen loads (hence giving time for resources to be loaded). The second image is when the splash screen is skipped, it still takes the same time to display the app content but then with no resources loaded and no styling.
I have no idea why this happens as it only happens when I export the app as an APK.
Have you tried running the app with
flutter run --release
Or you could run the app (with the exported apk) and run
flutter attach
This will show the app logs while running
Have you build apk release ?
try to build release app by run
flutter build apk --release
If your problem is not solved Share your project file or github link to better understand your problem and solve it for you
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.
Always getting white blank screen when running the app on the physical device in android case. Using react-native-navigation can't able to detect the bug please help!
I have created a fresh react-native project and integrated the react-native-navigation library into it and when I am running the app in my physical device by running the command yarn run android it runs but shows blank white screen in android. Once it runs successfully but now it won't.
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.
With some effort I finally managed to install Qt for Android and wrote my first testing app. Everything went ok when debugging(usb debugging on galaxy s5) but after deploying the app via "Bundle Qt libraries in APK" and installing+running it on the phone I encountered a problem.
The design of the app changes after the first time run. The left screenshot is how the app looks after installing and tapping 'Open'; the right one is made after closing the app via the back button and opening it again from the app drawer:
(The add button in the first image is blue because it was in focus)
As you can see, the slider(QSlider) theme changes, and the 'Add' button also gets smaller.
I've also built and deployed the app with the x86 kit(instead of armeabi-v7a) and installed it on Genymotion Nexus 5 emulator, getting the same strange behaviour.