You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
flutter version >1.9.1 not working on Android 4.4 and lower #47609
I tested on an SDK 16 emulator and master and couldn't reproduce an application crash. However I am consistently seeing the runner quitting even though the application on the emulator appears to run fine:
[ +9 ms] Error waiting for a debug connection: Bad state: No element
[ +1 ms] Error launching application on emulator-5554.
I checked the ADB logs and didn't see anything immediately obvious.
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
@jason-simmons says he also can't reproduce this on an API 16 physical device. @guit4eva if you have any additional details please add them and we can reopen this.
On Fri, 24 Jan 2020, 06:18 Flutter GitHub Bot, ***@***.***> wrote:
Closed #47609 <#47609> via #49327
<#49327>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#47609?email_source=notifications&email_token=AB2QQ53E5YPZNUGBK3VHDRDQ7JTX3A5CNFSM4J6LD4A2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWFRO2RI#event-2976050501>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2QQ52HSHLOO5JZ5LU6E7LQ7JTX3ANCNFSM4J6LD4AQ>
.
What would be the correct way to do this? I've tried git pull origin
pull/49327/head, which results in a lot of merge conflicts. Is there
another way to apply the PR locally - or automatically accept all incoming
changes?
On Wed, Jan 29, 2020 at 10:10 PM Dan Field ***@***.***> wrote:
No. In a pinch you can apply #49327
<#49327> locally until this can
arrive on stable.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#47609?email_source=notifications&email_token=AB2QQ57BCQOGYBQJTYGKECLRAHPDRA5CNFSM4J6LD4A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKISKII#issuecomment-579937569>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2QQ562AWGVKSFVL746QXLRAHPDRANCNFSM4J6LD4AQ>
.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v' please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.
What would be the correct way to do this? I've tried git pull origin pull/49327/head, which results in a lot of merge conflicts. Is there another way to apply the PR locally - or automatically accept all incoming changes? …
On Wed, Jan 29, 2020 at 10:10 PM Dan Field @.***> wrote: No. In a pinch you can apply #49327 <#49327> locally until this can arrive on stable. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#47609?email_source=notifications&email_token=AB2QQ57BCQOGYBQJTYGKECLRAHPDRA5CNFSM4J6LD4A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKISKII#issuecomment-579937569>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB2QQ562AWGVKSFVL746QXLRAHPDRANCNFSM4J6LD4AQ .
@guit4eva You can switch to the dev channel, which currently has the fix, but may not be as stable. If you want to be on a known stable (but may involve some manual intervention to make sure it makes sense), you can upgrade to the latest stable (v1.12.13+hotfix.7) and then git cherry-pick the fix revision.
@guit4eva can you check out the dev channel and confirm whether or not your error still occurs? I am thinking that your issue may be different from the one that @jason-simmons fixed in #49327 as I believe that regression was introduced after v1.12.13 stable was cut. If you are still getting a gradle build error I may have to re-open this issue.
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 flutter doctor -v and a minimal reproduction of the issue.
Activity
iapicca commentedon Dec 22, 2019
Hi @guit4eva
can you please provide your
flutter doctor -vand your
flutter run --verbose?Thank you
erlange commentedon Dec 27, 2019
The same happened to me also,
v1.9.1+hotfix.2seems to be the maximum version I'm confident with.mklim commentedon Jan 18, 2020
I tested on an SDK 16 emulator and master and couldn't reproduce an application crash. However I am consistently seeing the runner quitting even though the application on the emulator appears to run fine:
I checked the ADB logs and didn't see anything immediately obvious.
no-response commentedon Jan 18, 2020
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
dnfield commentedon Jan 18, 2020
@jason-simmons says he also can't reproduce this on an API 16 physical device. @guit4eva if you have any additional details please add them and we can reopen this.
guit4eva commentedon Jan 18, 2020
Hey there,
Here are the requested logs:
Flutter Run:
Flutter Doctor:
guit4eva commentedon Jan 29, 2020
dnfield commentedon Jan 29, 2020
No. In a pinch you can apply #49327 locally until this can arrive on stable.
guit4eva commentedon Jan 30, 2020
iapicca commentedon Feb 6, 2020
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v' please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.
christopherfujino commentedon Feb 6, 2020
@guit4eva You can switch to the dev channel, which currently has the fix, but may not be as stable. If you want to be on a known stable (but may involve some manual intervention to make sure it makes sense), you can upgrade to the latest stable (v1.12.13+hotfix.7) and then
git cherry-pickthe fix revision.christopherfujino commentedon Feb 11, 2020
@guit4eva can you check out the dev channel and confirm whether or not your error still occurs? I am thinking that your issue may be different from the one that @jason-simmons fixed in #49327 as I believe that regression was introduced after v1.12.13 stable was cut. If you are still getting a gradle build error I may have to re-open this issue.
github-actions commentedon Aug 23, 2021
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
flutter doctor -vand a minimal reproduction of the issue.