Steps to Reproduce
App crashes during launch on some devices with armeabi-v7a (ARM 32-bit) only. This crash started happening after upgrading to Flutter 3.
Crash Traces
Firebase Crashlytics does not pick up this crash, and the Play console's output is limited, but here it is:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> com.ebay.motorsapp <<<
backtrace:
#00 pc 0000000000a7409c /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000dced20 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000dcec98 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000001618b3c /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000ab563c /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000ab6df0 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000ab70a8 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000ab73f8 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000001101530 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000001100c24 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000ab60c4 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000ab68b8 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000ab6998 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 000000000161de9c /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000001622c8c /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 000000000161dbf0 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 00000000010f7e88 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 00000000010f7d80 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 00000000010f7d50 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000a75c54 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libapp.so (offset 0x1000)
#00 pc 0000000000468279 /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libflutter.so (offset 0x16aa000)
#00 pc 000000000017abfd /data/app/com.ebay.motorsapp-fD3CyntEkOFjDXfKSJWsBg==/split_config.armeabi_v7a.apk!lib/armeabi-v7a/libflutter.so (offset 0x16aa000)
Here's another example of a crash after reproducing in Firebase Test Lab -- we believe it's a similar (or same) crash as above:
06-22 11:07:01.115: A/libc(18851): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x36 in tid 18927 (1.ui)
06-22 11:07:01.170: A/DEBUG(316): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-22 11:07:01.171: A/DEBUG(316): Build fingerprint: 'motorola/harpia/harpia:6.0.1/MPIS24.241-2.50-16/16:user/release-keys'
06-22 11:07:01.171: A/DEBUG(316): Revision: 'p1b0'
06-22 11:07:01.171: A/DEBUG(316): ABI: 'arm'
06-22 11:07:01.171: A/DEBUG(316): pid: 18851, tid: 18927, name: 1.ui >>> com.ebay.motorsapp <<<
06-22 11:07:01.171: A/DEBUG(316): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x36
06-22 11:07:01.194: A/DEBUG(316): r0 9a366639 r1 a0e09eb4 r2 0000037a r3 9a366644
06-22 11:07:01.195: A/DEBUG(316): r4 00000002 r5 9ce0bee9 r6 9eb8e3d9 r7 9de89004
06-22 11:07:01.195: A/DEBUG(316): r8 00000037 r9 a142efb9 sl b897ea70 fp a0e09e08
06-22 11:07:01.195: A/DEBUG(316): ip 0000000a sp a0e09df4 lr 00000004 pc 9fe6909c cpsr 200d0010
06-22 11:07:01.196: A/DEBUG(316): backtrace:
06-22 11:07:01.196: A/DEBUG(316): #00 pc 0000009c /data/app/com.ebay.motorsapp-1/split_config.armeabi_v7a.apk (offset 0xa75000)
06-22 11:07:01.196: A/DEBUG(316): #01 pc 00000000 <unknown>
We cannot provide a minimal reproducible sample as we don't know how to reproduce the crash code-wise, it happens immediately during app launch, and it appears to be a low level issue.
Details
summary:
Flutter 3.0.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision fb57da5f94 (3 weeks ago) • 2022-05-19 15:50:29 -0700
Engine • revision caaafc5604
Tools • Dart 2.17.1 • DevTools 2.12.2
flutter doctor -v:
The output below is a close match to the CI env, the only difference being the Android toolchain SDK version was actually 29.0.3 not 30.0.3.
[✓] Flutter (Channel stable, 3.0.1, on macOS 11.6.5 20G527 darwin-x64, locale en-US)
• Flutter version 3.0.1 at /Users/<redacted>/Library/code/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision fb57da5f94 (5 weeks ago), 2022-05-19 15:50:29 -0700
• Engine revision caaafc5604
• Dart version 2.17.1
• DevTools version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/<redacted>/Library/Android/sdk/
• Platform android-31, build-tools 30.0.3
• ANDROID_SDK_ROOT = /Users/<redacted>/Library/Android/sdk/
• Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2020.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
[✓] VS Code (version 1.68.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.42.0
[✓] Connected device (3 available)
• iPhone 13 Pro Max (mobile) • B4223F7B-0519-4337-859A-D188D3F8034B • ios •
com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
• macOS (desktop) • macos • darwin-x64 • macOS 11.6.5 20G527 darwin-x64
• Chrome (web) • chrome • web-javascript • Google Chrome 102.0.5005.115
[✓] HTTP Host Availability
• All required HTTP hosts are available
• No issues found!
Steps to Reproduce
App crashes during launch on some devices with armeabi-v7a (ARM 32-bit) only. This crash started happening after upgrading to Flutter 3.
Crash Traces
Firebase Crashlytics does not pick up this crash, and the Play console's output is limited, but here it is:
Here's another example of a crash after reproducing in Firebase Test Lab -- we believe it's a similar (or same) crash as above:
We cannot provide a minimal reproducible sample as we don't know how to reproduce the crash code-wise, it happens immediately during app launch, and it appears to be a low level issue.
Details
summary:flutter doctor -v:
The output below is a close match to the CI env, the only difference being the Android toolchain SDK version was actually 29.0.3 not 30.0.3.