-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
Google Play Store: Native Crash for Flutter Sample Counter Project #105903
Comments
im going reproduce the error, will back to you soon, i think it flutter bug(not sure) |
@flutter-symbolizer-bot #105903 (comment) force flutter#v3.0.2 android release arm64 |
crash from #105903 (comment) symbolized using symbols for
|
I am facing the same issue with my project. |
I am also facing the same issue, any workaround for this. Build fingerprint: 'generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys' |
I have the same issue Build fingerprint: 'generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys' |
I have the same issue. As a temporary hack, If I set minSdkVersion to 29 it prevents Play Store from checking against the Pixel 2 (API 28) and allows “reviewing” to complete. Unfortunately this prevents my app from working on any device earlier than Android 10. |
This might be a flutter version issue and you can Try deploying with flutter 3.1.0 and dart version 2.18.0 although it's a beta version but I think the problem might be solved. |
@NdegwaJulius Thank you. This fixed my issue! You don't even have to add ndk filter. |
@NdegwaJulius @yasburg Would you please verify that using the 3.1.0 beta with minSdkVersion set to 28 (or earlier) passes the Play Store review? |
I am currently working on publishing on the playstore so I can only confirm that it passes the google play review. You can also use TestLab in firebase to check which takes a shorter time to verify (for google play).
|
Okay, thanks. I'll give it a try with the Play Store. |
@prgtrdr Yes it does |
This may be a documentation issue. We should investigate more to see if we simply need to mark certain ABIs as unavailable. |
@NdegwaJulius @yasburg Confirmed, using beta 3.1.0 solved the problem for me as well. Do you know what is in the beta that fixes it (so we can make sure it's in the eventual release)?
|
Created a new build today using Flutter 3.0.4 and I have the same issue. My previous build using Flutter 3.0.1 did not have this issue. |
@incon Use flutter 3.1.0(Beta) |
@NdegwaJulius When do the fixes land in stable? |
We are aware of this issue. Raising priority due to a large number of people experiencing this. |
Same problem here. |
Though the pre-crash report shows a native crash, I was able to release the app to production. |
@MarikIshtar007 What version of Flutter are you using, and what is minSdkVersion set to? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
also please share the steps to upgrade from flutter 2.8.0 and dart 2.13.0 to newer versions? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@prgtrdr I'm on flutter channel stable v2.10.3, dart version 2.16.1 flutter doctor -v output
And for the minSdkVersion, this is what I have in my gradle file..
|
This comment was marked as off-topic.
This comment was marked as off-topic.
Yes, it's the same issue. I'm going to close this as a duplicate to consolidate discussion there. I'll add a summary of status there. |
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 |
I am uploading my App to Google Play Store. I signed and had an app bundle built as shown in the flutter doc. I have included the following lines in the app/build.gradle stating that the ndk should only covers the following 'armeabi-v7a', 'arm64-v8a', 'x86_64', but when I upload the appbundle to Google Play Store, it always shows there is a Native Crash on the 'GCE x86 phone'. No matter I choose to release as any kind of testing or Production. The app is then put to 'reviewing' forever and not proceeding or launching publicly:
`
android {
compileSdkVersion 32
ndkPath = "/Users/xxx/Library/Android/sdk/ndk/24.0.8215888"
defaultConfig {
or even not supporting 'x86_64
ndk { abiFilters 'armeabi-v7a', 'arm64-v8a' }
Steps to Reproduce
Environments(tried on both, same problem happens):
Actual results:
Both Native Crash and ANR would occur
Code sample
Nothing has changed to the codes in the new flutter starter project
Logs
Native Crash Log
The text was updated successfully, but these errors were encountered: