-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Flutter create template crashes when run in Android Emulator SDK v19 #20091
Comments
Looks like this is the crash:
|
Presumably a regression in our engine? @jason-simmons or @chinmaygarde would know. |
This crash is happening during a call to Apparently older versions of the Android C runtime on x86 will crash if dlsym is called on a symbol name that is not present. (see https://users.rust-lang.org/t/libc-dlsym-crashing-on-i686-linux-android/14788/3) Recent versions of Android will have a fix for this |
FYI @zanderso |
Do you foresee this issue getting fixed soon? If not, is this an issue a random contributer like myself would be capable of fixing? I have some experience building native android apps and would be happy to help. I'm working on a project that must support android API level 19. I really want to use flutter but this would be a deal break for me. Thank you! I've been loving Flutter! |
Just wanted to confirm I'm also getting this issue. Is there anything a random contributer would be able to do? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Same problem here. Can't run anything within the emulator on API 19, or a physical device with API 19. |
I had this problem in flutter 0.10.x but not on flutter 1.1.2-pre.39 |
Here is a another stack trace |
Met this problem as well with |
@wald-tq Did you get there by using the
|
I am getting the same error. Any updates or temporary fixes, if there any ? |
Same error for me on API 19. Are there any fixes for this? Should I exclude API 19 in my project? |
This comment has been minimized.
This comment has been minimized.
@khashayarmotarjemi |
I'm still having this problem, any clear solution?
|
I'm still having this problem with API 19... |
does this also happen on physical devise or just emulator? and is there any fix for now? |
Yes, It has the same problem on samsung devices api 19.
…On Sat, 23 Feb 2019 at 23:55, khashayarmotarjemi ***@***.***> wrote:
does this also happen on physical devise or just emulator? and is there
any fix for now?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20091 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/As5uOgWz_OENeztXhCLtWixX2wkyZJOyks5vQbjRgaJpZM4Vq3ck>
.
|
SDK v19
On Sun, 24 Feb 2019, 12:58 a.m. Bashar Albashier <basharalbashier@gmail.com
wrote:
… Yes, It has the same problem on samsung devices api 19.
On Sat, 23 Feb 2019 at 23:55, khashayarmotarjemi ***@***.***>
wrote:
> does this also happen on physical devise or just emulator? and is there
> any fix for now?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#20091 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/As5uOgWz_OENeztXhCLtWixX2wkyZJOyks5vQbjRgaJpZM4Vq3ck>
> .
>
|
I've replaced MaterialApp with Scaffold and still having the problem. :( |
It also happened with flutter latest stable version 1.2.1, on HUAWEI Che2-TL00M, android 4.4.2. Here is the android studio log:
|
this is the output of nox emulator : logcat shows nothing and the emulator stays on white screen. |
any update ? i still have same problem :( |
I have same problem on my android physical device: here is the cash code: Launching lib/main.dart on LA2 SN in debug mode... Build fingerprint: 'xiaolajiao/LA2-SN/LA2-SN:4.4.4/KTU84P/20151117.152937:user/release-keys' |
The same issue here any news? |
the same error here with Samsung J110F |
same error |
i got same error, i'm using Tablet P10 with Android Level 19 |
same error here on SM P901 and all the emulators running KitKat, no update yet? |
When will update be available? All my Android clients on SDK v19 cannot use our app and that's very bad. |
We need some an update for this issue. |
any fix now? I'm working on flutter release 1.7, emulator android 4.4, and got the issue.
|
No any update for this issue??? 🤔 |
Currently running into this issue on API 19 on a Cipher Lab RS30, this is a huge issue for us |
fyi @cbracken |
The dynamic linker on some older versions of Android on x86 fails when doing dlsym(RTLD_DEFAULT) lookups of symbols exported by the engine library itself. The engine needs to do this for some data files that are linked into the engine library (ICU data and Dart snapshot blobs). To work around this, the engine will declare static symbols for these data objects on the affected platforms. Fixes flutter/flutter#20091
) The dynamic linker on some older versions of Android on x86 fails when doing dlsym(RTLD_DEFAULT) lookups of symbols exported by the engine library itself. The engine needs to do this for some data files that are linked into the engine library (ICU data and Dart snapshot blobs). To work around this, the engine will declare static symbols for these data objects on the affected platforms. Fixes flutter/flutter#20091
@jason-simmons has landed flutter/engine#11001. This should now be fixed on |
I'm on Channel beta, v1.8.3, running flutter it crashes on API 19 for me too |
I switched to the dev channel and it worked, I'm using flutter v1.9.7 try on terminal
|
same issue here with flutter v1.9.1 |
App crash in android 4.4 with flutter v1.9.1+hotfix.6 |
Same issue here |
I am also facing this issue |
Hi folks. We believe this issue has been addressed. If you're still seeing something that looks similar, please file a new issue with full details. Thanks! |
Hello, I am using the Flutter counter application, and when I try to run the emulator in the API 19 I return an error and for the application, I would like help for correcting this error, as I have not identified the error I will be putting the whole output message that is in LogCat in the description.
The text was updated successfully, but these errors were encountered: