-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[image picker] - Documentation needs fixes and more explanation #62304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @febg11
Can you also please provide your |
My code has quite a lot going on but the simplest example would be the example code provided but the flutter team... here.
This isnt a bug per say I am just struggling to find.a method to get what is called The read me states: I am just looking for a method that will force the MainActivity to be killed so I can actually debug what comes back in response.file. Being able to debug it will help al lot as its kind of broken my current process flow (which is fine). I don't really think my flutter run output will help as its would running the image picker example app just fine... I need a method to effectively force an error. Thanks for replying so quickly :) Side note |
Any update on this? its been quite a while |
For 3 @febg11 Add some debugprint in retrieveLostData Function after
you can enable dont keep activites in dev options and then push your app to background ,after selecting any image , as soon as you push it to background , the debug connection would be terminated , now run your app again , it should log the debugprint in the console hope it helps |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Hi,
I have recently updated my image picker version and I have encountered a few changes problems.
Correct me if I'm wrong but aren't these the wrong way around?
The version I was on also did not talk about MainActivity being destroyed by android in the readme... Is this a problem that was present on older versions or has this been caused by something in the newer versions of the imagepicker.
I am having trouble implementing my version of
retrieveLostData()
mainly because I cant seem to be able to recreate the error. Is there a method I can use that will force the Main Activity to be destroyed so I can test my future builder logic?Furthermore I use the provider package to manage my application state which I alter when picking images. I can't tell if i need to update state again when the main activity is destroyed or if the current data will persist (as it hasn't ever happened). I imagine the answer to number 3 will help answer this.
Please can you help debug this as I currently have code written that has never ran and I can't recreate a scenario that will cause
retrieveLostData()
to be called.The text was updated successfully, but these errors were encountered: