In https://github.com/flutter/flutter/pull/94137, the remote cloud path for the CIPD path (used to download the canvaskit bundle) can be overridden by the FLUTTER_STORAGE_BASE_URL env var. This was to allow maintainers of flutter artifact mirrors to include the canvaskit bundle in their mirror (https://github.com/flutter/flutter/issues/92357). However, if this env var is set to the default value, which is https://storage.googleapis.com, this will be the wrong namespace for cipd artifacts, which should be at https://chrome-infra-packages.appspot.com/dl.

I think the ideal solution here would be to publish the canvaskit bundle flutter depends to our own storage bucket, and not CIPD, so that it can be treated like any other engine artifact.

This bug is reproducible when you generate the app using in release mode and you open it in an x86 or arm32 emulator

If you are having issues opening an app on your x86 or arm32 emulator, you may be seeing the following error message: "{AppName} consistently crashes". This may be caused by the fact that Flutter does not support x86 files, as mentioned in this link: https://docs.flutter.dev/deployment/android#what-are-the-supported-target-architectures. According to the documentation, Flutter currently does not offer support for generating x86 files for Android (see Issue 9253).

This can be a particularly problematic when you are trying to use packages that depend on resources such as the camera or MLKit. To resolve this issue, you can edit the 'build.grandle' file in the 'app' folder and add the following lines to prevent the generation of x86 files:

   defaultConfig {
        ndk {
            abiFilters 'armeabi-v7a','arm64-v8a','x86_64'
        }
    }

This should help resolve the issue and allow you to open the app on the emulator without errors. It is important to remember that Flutter currently only supports the armeabi-v7a (ARM 32-bit), arm64-v8a (ARM 64-bit), and x86-64 (x86 64-bit) target architectures. Therefore, when editing the 'build.grandle' file, it is important to ensure that you are only including these architectures.

I get the following exception after typing text in textinput in a flutter windows app:

======== Exception caught by services library ====================================================== The following assertion was thrown during a platform message callback: A KeyRepeatEvent is dispatched, but the state shows that the physical key is not pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in HardwareKeyboard. This was the event: KeyRepeatEvent#7e93e(physicalKey: PhysicalKeyboardKey#700e1(usbHidUsage: "0x000700e1", debugName: "Shift Left"), logicalKey: LogicalKeyboardKey#00102(keyId: "0x200000102", keyLabel: "Shift Left", debugName: "Shift Left"), character: null, timeStamp: 478:41:15.438993) 'package:flutter/src/services/hardware_keyboard.dart': Failed assertion: line 432 pos 16: '_pressedKeys.containsKey(event.physicalKey)'

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause. In either case, please report this assertion by filing a bug on GitHub: https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack: #2 HardwareKeyboard._assertEventIsRegular. (package:flutter/src/services/hardware_keyboard.dart:432:16) #3 HardwareKeyboard._assertEventIsRegular (package:flutter/src/services/hardware_keyboard.dart:443:6) #4 HardwareKeyboard.handleKeyEvent (package:flutter/src/services/hardware_keyboard.dart:535:5) #5 KeyEventManager.handleRawKeyMessage (package:flutter/src/services/hardware_keyboard.dart:881:37) #6 BasicMessageChannel.setMessageHandler. (package:flutter/src/services/platform_channel.dart:197:49) #7 _DefaultBinaryMessenger.setMessageHandler. (package:flutter/src/services/binding.dart:387:35) #8 _invoke2 (dart:ui/hooks.dart:186:13) #9 _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5) #10 _Channel.push (dart:ui/channel_buffers.dart:132:31) #11 ChannelBuffers.push (dart:ui/channel_buffers.dart:329:17) #12 PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:599:22) #13 _dispatchPlatformMessage (dart:ui/hooks.dart:89:31) (elided 2 frames from class _AssertionError)

Unable to parse JSON message: The document is empty.

======== Exception caught by services library ====================================================== The following assertion was thrown during a platform message callback: A KeyRepeatEvent is dispatched, but the state shows that the physical key is not pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in HardwareKeyboard. This was the event: KeyRepeatEvent#7e93e(physicalKey: PhysicalKeyboardKey#700e1(usbHidUsage: "0x000700e1", debugName: "Shift Left"), logicalKey: LogicalKeyboardKey#00102(keyId: "0x200000102", keyLabel: "Shift Left", debugName: "Shift Left"), character: null, timeStamp: 478:41:15.438993) 'package:flutter/src/services/hardware_keyboard.dart': Failed assertion: line 432 pos 16: '_pressedKeys.containsKey(event.physicalKey)'

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause. In either case, please report this assertion by filing a bug on GitHub: https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack: #2 HardwareKeyboard._assertEventIsRegular. (package:flutter/src/services/hardware_keyboard.dart:432:16) #3 HardwareKeyboard._assertEventIsRegular (package:flutter/src/services/hardware_keyboard.dart:443:6) #4 HardwareKeyboard.handleKeyEvent (package:flutter/src/services/hardware_keyboard.dart:535:5) #5 KeyEventManager.handleRawKeyMessage (package:flutter/src/services/hardware_keyboard.dart:881:37) #6 BasicMessageChannel.setMessageHandler. (package:flutter/src/services/platform_channel.dart:197:49) #7 _DefaultBinaryMessenger.setMessageHandler. (package:flutter/src/services/binding.dart:387:35) #8 _invoke2 (dart:ui/hooks.dart:186:13) #9 _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5) #10 _Channel.push (dart:ui/channel_buffers.dart:132:31) #11 ChannelBuffers.push (dart:ui/channel_buffers.dart:329:17) #12 PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:599:22) #13 _dispatchPlatformMessage (dart:ui/hooks.dart:89:31) (elided 2 frames from class _AssertionError)

flutter: Wine Unable to parse JSON message: The document is empty.

======== Exception caught by services library ====================================================== The following assertion was thrown during a platform message callback: A KeyRepeatEvent is dispatched, but the state shows that the physical key is not pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in HardwareKeyboard. This was the event: KeyRepeatEvent#7e93e(physicalKey: PhysicalKeyboardKey#700e1(usbHidUsage: "0x000700e1", debugName: "Shift Left"), logicalKey: LogicalKeyboardKey#00102(keyId: "0x200000102", keyLabel: "Shift Left", debugName: "Shift Left"), character: null, timeStamp: 478:41:15.438993) 'package:flutter/src/services/hardware_keyboard.dart': Failed assertion: line 432 pos 16: '_pressedKeys.containsKey(event.physicalKey)'

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause. In either case, please report this assertion by filing a bug on GitHub: https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack: #2 HardwareKeyboard._assertEventIsRegular. (package:flutter/src/services/hardware_keyboard.dart:432:16) #3 HardwareKeyboard._assertEventIsRegular (package:flutter/src/services/hardware_keyboard.dart:443:6) #4 HardwareKeyboard.handleKeyEvent (package:flutter/src/services/hardware_keyboard.dart:535:5) #5 KeyEventManager.handleRawKeyMessage (package:flutter/src/services/hardware_keyboard.dart:881:37) #6 BasicMessageChannel.setMessageHandler. (package:flutter/src/services/platform_channel.dart:197:49) #7 _DefaultBinaryMessenger.setMessageHandler. (package:flutter/src/services/binding.dart:387:35) #8 _invoke2 (dart:ui/hooks.dart:186:13) #9 _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5) #10 _Channel.push (dart:ui/channel_buffers.dart:132:31) #11 ChannelBuffers.push (dart:ui/channel_buffers.dart:329:17) #12 PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:599:22) #13 _dispatchPlatformMessage (dart:ui/hooks.dart:89:31) (elided 2 frames from class _AssertionError)

Flutter doctor:

[√] Flutter (Channel stable, 3.3.5, on Microsoft Windows [Version 10.0.19044.2364], locale de-DE) • Flutter version 3.3.5 on channel stable at C:\SDKs\flutter_latest\flutter • Upstream repository https://github.com/flutter/flutter.git • Framework revision d9111f6402 (3 months ago), 2022-10-19 12:27:13 -0700 • Engine revision 3ad69d7be3 • Dart version 2.18.2 • DevTools version 2.15.0

In Material 3, when setting appBarTheme.actionsIconTheme or appBarTheme.iconTheme overrides, the color values will be overridden by any iconButtonTheme also present in the theme.

This means that users cannot set different app-wide theme overrides for app bar leading and trailing IconButton widgets, which would be expected from the names of actionsIconTheme/iconTheme. While users can provide their own leading/trailing widgets, the app bar itself constructs menu, back and close IconButtons.

This is due to the app bar using IconButton widgets, which defer to Theme.iconButtonTheme for color properties in M3. I think the app bar IconButtons need to have a local override which prioritises appBarTheme icon theme values.

Example at https://dartpad.dev/?id=d9b90b67d6bc18b09b9309c09080355a&channel=beta

This only occurs in Material 3 (try commenting out useMaterial3 in example above).

Part of https://github.com/flutter/flutter/issues/117844

• [ ] url_launcher_android
• [ ] url_launcher_ios
• [ ] url_launcher_linux - Blocked on https://github.com/flutter/flutter/issues/73740
• [ ] url_launcher_macos - likely blocked on https://github.com/flutter/flutter/issues/112483
• [ ] url_launcher_windows