I just build my apk to test it on the phone but I got some weird errors like
the dialogue box that opened on the onTap method stopped working but before or in the debug mode it is still working.
the image picker has the same problem that it is not working in apk but it is working when running through android studio.
does anyone know any reason behind this is why this is happening?
it would be really helpful if you could help.
For some design issue it may occure in release mode. Where in debug mode we get some warning and ignore that but in release mode without solving those design issue it won't run smoothly. try to find if there has any design issue like
'Incorrect use of ParentDataWidget.'
So solution is
Run you app in debug mode and check logs, I am sure you will find the problem there.
Related
I am using Firebase in my project to get the data. Problem is when I run debug version app works fine and show the fetched data but when I create a release version of it and then open my application It's shows blank screen. It is strange and I am not getting why this happening. To understand the issue I have given the two videos of it and also the project repository link, and the problem I am facing in the Book_Screen.dart.
Project Link: https://github.com/jaydip-pawar/Hindi-Audio-Bible
In Debug Version:
In Release Version:
It is hard to catch problem in release mode. But you can try to open "Uncaught Exception" from the debug panel and if some error occurs, try to fix them.
If you can't solve the problem, you can comment widgets one by one. In this way, you can look for the specific lines of code that causes the error.
If you are using playstore inbuilt keystore, add those sha1 from playstore to firebase app setting.
The app I have created seems to open quite slow (and janky) compared to other apps on my phone. It only seems to happen on android
I have tried copying the dependencies to a new project and running it and it doesn't replicate the same behaviour.
I have also changed the original app to only load a red container in the matierial app but its still really choppy on app launch before it loads.
I would post some code but I am not entirely sure whats wrong.
Sorry this is quite vague but I am running out of ideas. I dont really want to have to recreate everything in a new project.
Please note I have done the android v2 migration so it could potentially be linked to this?
Does anyone have any ideas to what could be causing it?
Update:
Forgot to mention this is on profile/release mode.. its not debug mode causing it
Well, it's hard to know why your app is being so "janky" but i'm going to make a few shots in the dark:
Are you running this on an emulator or on a real phone? Emulators will sometimes act weird, and will deliver results that you might not see on an actual android device. If you are running this on an emulator, try launching it on a physical phone. I have had experience with using Android emulators and sometimes trying to open the app at all becomes weird. How old your phone is might also be the cause of this, if it is old.
Do you have too many tabs open? Try exiting out of all of your applications and then open up your flutter app. See if that does anything.
That is all that I have concerning the environment that you are working in. You haven't posted any code, so i'm going to have to ask you about what your app is doing on startup. It would be good if you posted some code or a link to a git repository so that I can see that and be of better help.
What do I do about this?
Xcode launches the app on the device and it starts up, but when it has started the image below pops up and when I click "OK" it crashes the app.
The simulator has no issues, but I cannot read the console in regards to debugging because of this. There really is not a reason why this should be happening.
Also I have no idea what code could cause this. I have no errors or warnings and everything has been fine right up until yesterday.
If there is any code or more info you need to help me with this, please ask:-)
I have removed the app, restarted the devices and my mac.
Ok I found the answer here:
Same issue here
Basically you can't do debugging on a Ad-Hoc profile:-)
I have an application of which i have created .ipa file and tried to run the application on iOS5. If i run it on iOS 5, it works but when i try to run it on iOS4.2 it doesn't work. It opens up, shows black window and then back to home screen. I have tried things like deleting app, installing again, restarting phone, reseting it's setting.
I know most people face vice a versa situation. Let me know if any one of you have good solution for it.
Thank you,
Anks
Your only hope is the console, see what it says about why it is dying. If that doesn't give any messages, stop it in the debugger in AplicationDidFinishLaunching, and step as far as you can...
The console though SHOULD have a message about why the app is terminating early. Without knowing why, we cannot help further.
Did you change your build target immediately before creating the .ipa? If so, do a clean build and then re-create the .ipa file again—that may fix your problem.
I am unable to debug my project as the breakpoints are not working.
I have enabled breakpoint option but still its not helping me.
I found some links but they are for the Xcode3
And for Xcode4 I found this site but it doesn't have any solution.
What should I do ?
Open Scheme drop box
Click on Edit Scheme
Click on Run YOURAPP.app tab on the left
Set Build Configuration to DEBUG
Set Debugger to LLDB
Enable breakpoints and Run the app
Ran face first into this problem after updating to iOS SDK 6.1. After a few hours of swearing and digging through settings, it seems to only happen when using LLDB. Switching to GDB has bestowed upon me the ability to use breakpoints again. FWIW I've had other issues with LLDB not correctly following vtable pointers. Good luck.
Try rebooting your device.
I had the same problem with Xcode4; although, I seem to remember it working before upgrading my phone to 6.1.
Anyhow, the suggestion here to reboot my device solved the problem. Breakpoints are again working for me.