Develop Reference

What is the reason for this below abort error in Android

This error was caught by Sentry. Is there any way to find what causes this error so it can be handled. Let me know if more
OS Version: Android 9 (F10_ALL_V1.0.3_202110260012)
Report Version: 104
Exception Type: Unknown (SIGABRT)
Application Specific Information:
Abort
Thread 0 Crashed:
0 libc.so 0x7386a3b0ac abort
1 libart.so 0x7303f6931c art::Runtime::Abort
2 libbase.so 0x7386448ce0 android::base::LogMessage::~LogMessage
3 libart.so 0x7303de9e80 art::JavaVMExt::JniAbort
4 libart.so 0x7303e5827c <unknown> + 493986611836
5 base.apk 0x72e319fb10 <unknown> + 493436402448
6 base.odex 0x72e58c7260 <unknown> + 493477458528

Unable to run Flutter App on iPhone 11 Pro after upgrading to Flutter 2

I upgraded to Flutter 2 and when I run App on iPhone 11 Pro on Android Studio I get the error below. Running the App on Xcode works fine. Didn't have this problem until I upgraded to Flutter 2.
Failed to build iOS app
Error output from Xcode build:
↳
2021-03-28 20:58:47.597 xcodebuild[26509:183755] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTiOSFrameworks/DVTiOSFrameworks-17705/DTDeviceKitBase/DTDKRemoteDeviceData.m:371
Details: (null) deviceType from 00008030-001A5D3221BB802E was NULL when -platform called.
Object: <DTDKMobileDeviceToken: 0x7f9889e5e380>
Method: -platform
Thread: <NSThread: 0x7f9888030a60>{number = 2, name = (null)}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2021-03-28 20:58:47.815 xcodebuild[26509:184029] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTiOSFrameworks/DVTiOSFrameworks-17705/DTDeviceKitBase/DTDKRemoteDeviceData.m:371
Details: (null) deviceType from 00008030-001A5D3221BB802E was NULL when -platform called.
Object: <DTDKMobileDeviceToken: 0x7f9889e5e380>
Method: -platform
Thread: <NSThread: 0x7f9889b8ef80>{number = 10, name = (null)}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2021-03-28 20:58:47.924 xcodebuild[26509:184029] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTiOSFrameworks/DVTiOSFrameworks-17705/DTDeviceKitBase/DTDKRemoteDeviceData.m:371
Details: (null) deviceType from 00008030-001A5D3221BB802E was NULL when -platform called.
Object: <DTDKMobileDeviceToken: 0x7f9889e5e380>
Method: -platform
Thread: <NSThread: 0x7f9889b8ef80>{number = 10, name = (null)}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2021-03-28 20:59:08.937 xcodebuild[26509:183961] DTDeviceKit: Failed to mount DDI from 'DVTFilePath:0x7f988a733370:'/Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/DeviceSupport/7.2/DeveloperDiskImage.dmg'', error=-402653035: Error Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage, NSUnderlyingError=0x7f9889f3f870 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653035 "The device rejected the pairing attempt." UserInfo={MobileDeviceErrorCode=(0xE8000095), com.apple.dtdevicekit.stacktrace=(
0 DTDeviceKitBase 0x0000000111769c8f DTDKCreateNSErrorFromAMDErrorCode + 220
1 DTDeviceKitBase 0x00000001117a5e8f -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 1024
2 DTDeviceKitBase 0x00000001117a68af __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 609
3 libdispatch.dylib 0x00007fff7266d658 _dispatch_client_callout + 8
4 libdispatch.dylib 0x00007fff726796ec _dispatch_lane_barrier_sync_invoke_and_complete + 60
5 DTDeviceKitBase 0x00000001117a65ec -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 188
6 IDEiOSSupportCore 0x0000000110f7554c __28-[DVTiOSDevice attachToken:]_block_invoke_5 + 277
7 DVTFoundation 0x0000000100a0517e DVT_CALLING_CLIENT_BLOCK + 7
8 DVTFoundation 0x0000000100a06da0 __DVTDispatchAsync_block_invoke + 1191
9 libdispatch.dylib 0x00007fff7266c6c4 _dispatch_call_block_and_release + 12
10 libdispatch.dylib 0x00007fff7266d658 _dispatch_client_callout + 8
11 libdispatch.dylib 0x00007fff7266f818 _dispatch_continuation_pop + 414
12 libdispatch.dylib 0x00007fff7266ef16 _dispatch_async_redirect_invoke + 703
13 libdispatch.dylib 0x00007fff7267b957 _dispatch_root_queue_drain + 326
14 libdispatch.dylib 0x00007fff7267c097 _dispatch_worker_thread2 + 92
15 libsystem_pthread.dylib 0x00007fff728c79f7 _pthread_wqthread + 220
16 libsystem_pthread.dylib 0x00007fff728c6b77 start_wqthread + 15
),

Android Studio Emulator: emulator64-crash-service quit unexpectedly

Configuration
I have a Macbook Pro (Retina, 13 inch, 2016) that is running macOS Big Sur 11.1
Bug Report
Android Studio always results in a crash (emulator64-crash-service quit unexpectedly.)
Before upgrading to macOS Big Sur, Android Emulator was working well. But since I upgraded the OS, Android emulators always crash.
Using both the AVD Manager in Android Studio and the Terminal, the AVD crashes with these logs:
./emulator -netdelay none -netspeed full -avd Pixel_API_28
emulator: Android emulator version 30.3.5.0 (build_id 7033400) (CL:N/A)
handleCpuAcceleration: feature check for hvf
emulator: WARNING: Running on a system with less than 6 logical cores. Setting number of virtual cores to 1
2021-01-21 11:51:29.242 qemu-system-x86_64[17602:214627] ApplePersistence=YES
The program exits without any additional logs so there is no way to identify the root cause.
And after that, a problem report is opened stating that emulator64-crash-service quit unexpectedly
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [17603]
VM Regions Near 0:
-->
__TEXT 10f359000-1103a1000 [ 16.3M] r-x/rwx SM=COW /Users/*/Library/Android/*
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libdispatch.dylib 0x00007fff201afaa6 dispatch_release + 4
1 com.apple.AppKit 0x00007fff236b66df -[NSPersistentUIManager dealloc] + 37
2 com.apple.AppKit 0x00007fff22c72880 -[NSPersistentUIManager initWithBundleID:] + 384
3 com.apple.Foundation 0x00007fff2118a04c _NSFaultInObject + 27
4 com.apple.HIToolbox 0x00007fff286c8ba9 _HIPersistentUICreatePersistentWindow + 46
5 com.apple.HIToolbox 0x00007fff286c8aba WindowStateSetMenuBarState(unsigned int, double, void const*) + 43
6 com.apple.HIToolbox 0x00007fff286b8ee5 MBWindows::CreateWindow(CGRect, unsigned int) + 373
7 com.apple.HIToolbox 0x00007fff286b8c69 MBWindows::GetWindowOnDisplay(unsigned int, unsigned char) + 183
8 com.apple.HIToolbox 0x00007fff286b8abd MenuBarInstance::ForEachWindowDo(unsigned char, bool (OpaqueWindowPtr*, unsigned int) block_pointer) + 183
9 com.apple.HIToolbox 0x00007fff286b89c3 MenuBarInstance::SetBoundsAndUpdateResolution() + 103
10 com.apple.HIToolbox 0x00007fff286b8571 MenuBarInstance::Show(MenuBarAnimationStyle, unsigned char, unsigned char, unsigned char, unsigned char) + 275
11 com.apple.HIToolbox 0x00007fff286b7fb8 MenuBarInstance::UpdateAggregateUIMode(MenuBarAnimationStyle, unsigned char, unsigned char, unsigned char) + 798
12 com.apple.HIToolbox 0x00007fff286b7bba MenuBarInstance::ForEachMenuBarDo(void (MenuBarInstance*) block_pointer) + 46
13 com.apple.HIToolbox 0x00007fff286b7b5a UpdateAllAggregateUIModes(MenuBarAnimationStyle, unsigned char) + 126
14 com.apple.HIToolbox 0x00007fff286b7ac6 SetSystemUIMode + 165
15 com.apple.AppKit 0x00007fff22fee43b -[NSApplication _setPresentationOptions:instance:flags:] + 1010
16 libqcocoa.dylib 0x00000001133bfc14 QCocoaIntegration::QCocoaIntegration(QStringList const&) + 1796
17 libqcocoa.dylib 0x00000001133bf23e QCocoaIntegrationPlugin::create(QString const&, QStringList const&) + 78
18 libQt5GuiAndroidEmu.5.12.1.dylib 0x0000000111c79c26 QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) + 198
19 libQt5GuiAndroidEmu.5.12.1.dylib 0x0000000111c85d69 QGuiApplicationPrivate::createPlatformIntegration() + 2473
20 libQt5GuiAndroidEmu.5.12.1.dylib 0x0000000111c8707b QGuiApplicationPrivate::createEventDispatcher() + 27
21 libQt5CoreAndroidEmu.5.12.1.dylib 0x000000011169e74f QCoreApplicationPrivate::init() + 1567
22 libQt5GuiAndroidEmu.5.12.1.dylib 0x0000000111c823c9 QGuiApplicationPrivate::init() + 57
23 libQt5WidgetsAndroidEmu.5.12.1.dylib 0x000000011238a4ba QApplicationPrivate::init() + 26
24 emulator64-crash-service 0x000000010f361ec5 main + 1285
25 libdyld.dylib 0x00007fff20376621 start + 1
Thread 1:
0 libsystem_pthread.dylib 0x00007fff20357458 start_wqthread + 0
Thread 2:
0 libsystem_pthread.dylib 0x00007fff20357458 start_wqthread + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x011dffff8839de21 rbx: 0x00007f930b53ab10 rcx: 0x0080000000000000 rdx: 0x0100000000000000
rdi: 0x0000000000000000 rsi: 0x00007fff7c59fd2c rbp: 0x00007ffee08a5480 rsp: 0x00007ffee08a5480
r8: 0x00000000000036be r9: 0x00000000000036c2 r10: 0x00007fff8839de22 r11: 0x00007fff236b66ba
r12: 0x0000000000000e6c r13: 0x00007f930b523720 r14: 0x00007fff201f99a0 r15: 0x0000000000000000
rip: 0x00007fff201afaa6 rfl: 0x0000000000010246 cr2: 0x0000000000000000
Logical CPU: 2
Error Code: 0x00000004 (no mapping for user data read)
Trap Number: 14
I looked up possible issues in Qt or Qemu but I have no idea what's the issue here and how it could be related to MacOS Big Sur
I tried uninstalling and reinstalling:
Android Studio
Intel x86 Emulator Accelerator (HAXM installer)
I also tried to Wipe data and cold boot the AVDs
Please advise if anyone has encountered this issue recently

Try removing Android cache directory
/Users/[useraccountname]/.android

How to add Android SDK to Intellij?

I installed Android Studio, got the path to the SDK (/Users/welf/Library/Android/sdk), added JDK to IntelliJ, clicked "Add Android SDK", navigated to the path above, selected... and then IntelliJ quits unexpectedly. Every time. With this output... Why? What to do?
Process: idea [7678]
Path: /Applications/IntelliJ IDEA CE.app/Contents/MacOS/idea
Identifier: com.jetbrains.intellij.ce
Version: 2020.2.1 (IC-202.6948.69)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: idea [7678]
User ID: 501
Date/Time: 2020-09-16 21:50:18.094 +0200
OS Version: Mac OS X 10.16 (20A5364e)
Report Version: 12
Bridge OS Version: 3.0 (14Y908)
Anonymous UUID: 3E55EF41-A528-C1D5-99E4-06C437DD47CC
Sleep/Wake UUID: 5132E6E7-1E44-4E90-92D6-20185BA86220
Time Awake Since Boot: 9600 seconds
Time Since Wake: 150 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000f8
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0xf8:
-->
__TEXT 106014000-10601a000 [ 24K] r-x/rwx SM=COW /Applications/IntelliJ IDEA CE.app/Contents/MacOS/idea
Application Specific Information:
abort() called
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff2231c50a __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff2241c671 pthread_kill + 263
2 libsystem_c.dylib 0x00007fff224de740 abort + 120
3 libjvm.dylib 0x00000001084a8734 os::abort(bool, void*, void const*) + 22
4 libjvm.dylib 0x00000001085facf1 VMError::report_and_die(int, char const*, char const*, __va_list_tag*, Thread*, unsigned char*, void*, void*, char const*, int, unsigned long) + 2953
5 libjvm.dylib 0x00000001085fa142 VMError::report_and_die(Thread*, unsigned int, unsigned char*, void*, void*, char const*, ...) + 152
6 libjvm.dylib 0x00000001085fad8d VMError::report_and_die(Thread*, unsigned int, unsigned char*, void*, void*) + 33
7 libjvm.dylib 0x00000001084ac669 JVM_handle_bsd_signal + 774
8 libjvm.dylib 0x00000001084aa1b5 signalHandler(int, __siginfo*, void*) + 45
9 libsystem_platform.dylib 0x00007fff224edd7d _sigtramp + 29
10 ??? 0x000000000000ffff 0 + 65535
11 com.apple.AppKit 0x00007fff2505e6db -[NSApplication run] + 765
12 libosxapp.dylib 0x000000010e0a24f0 +[NSApplicationAWT runAWTLoopWithApp:] + 222
13 libawt_lwawt.dylib 0x000000010e004ab2 +[AWTStarter starter:headless:] + 834
14 com.apple.JavaNativeFoundation 0x00007fff6693870f +[JNFRunLoop _performCopiedBlock:] + 15
15 com.apple.Foundation 0x00007fff23329fa9 __NSThreadPerformPerform + 204
16 com.apple.CoreFoundation 0x00007fff2265a4bc __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
17 com.apple.CoreFoundation 0x00007fff2265a424 __CFRunLoopDoSource0 + 180
18 com.apple.CoreFoundation 0x00007fff2265a19f __CFRunLoopDoSources0 + 248
19 com.apple.CoreFoundation 0x00007fff22658bd1 __CFRunLoopRun + 890
20 com.apple.CoreFoundation 0x00007fff2265816e CFRunLoopRunSpecific + 563
21 com.jetbrains.intellij.ce 0x0000000106015bf5 main + 332
22 libdyld.dylib 0x00007fff22437951 start + 1
...

Better install Android Studio which downloads or recognizes the existing Android SDK for you to use in installation step. So you don't need to do it explicitly with Intellij Studio.
If you want flutter then Android Studio comes with plugin for it.

Looks like the crash is caused by JCEF which is bundled with the IDE Java Runtime: JBR-2377. Try to add ide.browser.jcef.enabled==false into IDE .properties file (Help | Edit Custom Properties... action) and restart IDE.

Android AVD can only be launched ONCE

...and every subsequent attempt at launching after that results in a crash. Once any AVD is launched and quit, it can never be launched successfully again. I've tried ARM and Intel ABIs, with and without snapshots. Nothing seems to make a difference.
I can't even delete that AVD from the AVD Manager's list; it claims it's "currently running in an emulator and can't be deleted", which is it not (there's no emulator process running). I have to manually delete the .avd files from ~/.android/avd/, and then create an entirely new AVD. I see no other process than the Android Studio app running (at least nothing that looks remotely related), but when I quit it, it asks me if I want to "disconnect from the process 'app'" (it asks multiple times, actually), even though Activity Monitor shows no process named "app". The emulator continues to crash after quitting and restarting Android Studio, as well as the machine itself.
None of the other AVD-related posts on SO seem to be relevant.
I'm running the latest version of Android Studio (just updated to 0.8.2 via the built-in updater), on the latest version of OS X Mavericks. Here's the interesting part of the stack trace of the crash:
Process: emulator64-arm [10831]
Path: /Users/USER/*/Android Studio.app/sdk/tools/emulator64-arm
Identifier: emulator64-arm
Version: ???
Code Type: X86-64 (Native)
Parent Process: studio [3462]
Responsible: studio [3462]
User ID: 501
Date/Time: 2014-07-09 14:17:37.966 -0600
OS Version: Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: B18B64F8-4A66-F624-243B-2AE2C192F57D
Sleep/Wake UUID: EE9F3B06-E894-4CA3-A022-8D4FC325A1BC
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT 000000010b732000-000000010b966000 [ 2256K] r-x/rwx SM=COW /Users/USER/*/Android Studio.app/sdk/tools/emulator64-arm
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 emulator64-arm 0x000000010b8ae18a 0x10b732000 + 1556874
1 com.apple.AppKit 0x00007fff8f457321 __67-[NSWindow _updateSettingsSendingScreenChangeNotificationIfNeeded:]_block_invoke + 237
2 com.apple.AppKit 0x00007fff8f4571e8 NSPerformWithScreenUpdatesDisabled + 65
3 com.apple.AppKit 0x00007fff8f457197 -[NSWindow _updateSettingsSendingScreenChangeNotificationIfNeeded:] + 197
4 com.apple.AppKit 0x00007fff8f44f491 -[NSWindow _setFrame:updateBorderViewSize:] + 914
5 com.apple.AppKit 0x00007fff8f44ea0e -[NSWindow _oldPlaceWindow:] + 652
6 com.apple.AppKit 0x00007fff8f44de3c -[NSWindow _setFrameCommon:display:stashSize:] + 1633
7 com.apple.AppKit 0x00007fff8f46225c -[NSWindow setFrameOrigin:] + 369
8 emulator64-arm 0x000000010b8abeb4 0x10b732000 + 1547956
9 emulator64-arm 0x000000010b8a8e95 SDL_SetVideoMode + 469
10 emulator64-arm 0x000000010b77749b 0x10b732000 + 283803
11 emulator64-arm 0x000000010b778aa8 0x10b732000 + 289448
12 emulator64-arm 0x000000010b778d4e skin_window_create + 190
13 emulator64-arm 0x000000010b77b471 0x10b732000 + 300145
14 emulator64-arm 0x000000010b742599 qemu_main + 5833
15 emulator64-arm 0x000000010b74d656 SDL_main + 6086
16 emulator64-arm 0x000000010b8b0270 0x10b732000 + 1565296
17 com.apple.CoreFoundation 0x00007fff9726ce0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
18 com.apple.CoreFoundation 0x00007fff9716082d _CFXNotificationPost + 2893
19 com.apple.Foundation 0x00007fff8ac407ba -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
20 com.apple.AppKit 0x00007fff8f334b69 -[NSApplication _postDidFinishNotification] + 289
21 com.apple.AppKit 0x00007fff8f33489c -[NSApplication _sendFinishLaunchingNotification] + 195
22 com.apple.AppKit 0x00007fff8f331786 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 570
23 com.apple.AppKit 0x00007fff8f3311db -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 242
24 com.apple.Foundation 0x00007fff8ac5ef0a -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 294
25 com.apple.Foundation 0x00007fff8ac5ed7d _NSAppleEventManagerGenericHandler + 106
26 com.apple.AE 0x00007fff8c91ae1f aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 381
27 com.apple.AE 0x00007fff8c91ac32 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 31
28 com.apple.AE 0x00007fff8c91ab36 aeProcessAppleEvent + 315
29 com.apple.HIToolbox 0x00007fff8e098161 AEProcessAppleEvent + 56
30 com.apple.AppKit 0x00007fff8f32d0b6 _DPSNextEvent + 1026
31 com.apple.AppKit 0x00007fff8f32c89b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
32 com.apple.AppKit 0x00007fff8f32099c -[NSApplication run] + 553
33 emulator64-arm 0x000000010b8b0917 main + 1351
34 emulator64-arm 0x000000010b7377e4 start + 52
Any tips/voodoo magic/suggestions on fixing this would be greatly appreciated.

Answering my own question for posterity...
Further investigation reveals that quitting the AVD process while its window is on an external monitor is the cause of the crash. Doing so saves the position of the window to the "emulator-user.ini" file within the AVD's .avd directory, and when this value is larger than the main screen's bounds, the AVD will crash upon launch. Editing this value to one that is within the main screen's bounds will allow the AVD to successfully launch again.
Bug reported: https://code.google.com/p/android/issues/detail?id=73364.