)]}'
{
  "commit": "a783556ebe75dc1cafbbf0a5778f2eeb71f3e166",
  "tree": "a614eb04b9b302010d603e41c78a0538fce10680",
  "parents": [
    "2cb26f7500f7a17e87f00d0f3077f1eccad3ed91"
  ],
  "author": {
    "name": "Chris Bracken",
    "email": "chris@bracken.jp",
    "time": "Sat Aug 08 06:20:42 2026 +0900"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Aug 07 21:20:42 2026 +0000"
  },
  "message": "iOS: Remove the non-merged thread topology (#190698)\n\niOS runs with the platform and UI threads merged, and it\u0027s not possible\nto create an engine with unmerged platform/ui threads, but\n`FlutterEngine` still included branches to create the unmerged threads\nwhen `Settings::merged_platform_ui_thread` wasn\u0027t enabled.\n\nThe option to opt-out of merged threads on iOS was removed in #174408 in\nAug 2025, and it had been the default configuration for over a year at\nthat point.\n\nBoth existing routes to a non-merged thread configuration already failed\nat startup:\n\n* Setting `FLTEnableMergedPlatformUIThread\u003dfalse` in Info.plist causes\nan `FML_CHECK` in `FlutterDartProject.mm` to blow up.\n* Setting `--no-enable-merged-platform-ui-thread` or\n`--merged-platform-ui-thread\u003ddisabled` results in them being parsed into\nSettings::merged_platform_ui_thread in `SettingsFromCommandLine`, and\ntriggers the same `FML_CHECK`.\n\nThe only route that didn\u0027t trigger an abort() on startup was\n`-[FlutterDartProject initWithSettings:]`, which is declared in\n`FlutterDartProject_Internal.h` and isn\u0027t part of the framework\u0027s public\nAPI.\n\nThis also removes the last place the iOS embedder checked\n`Settings::enable_impeller`. Now it\u0027s simply assumed.\n\nThis is part of cleanup work intended to simplify the iOS embedder prior\nto an eventual migration to the embedder API.\n\nIssue: https://github.com/flutter/flutter/issues/112232\n\n\u003c!--\nThanks for filing a pull request!\nReviewers are typically assigned within a week of filing a request.\nTo learn more about code review, see our documentation on Tree Hygiene:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md\n--\u003e\n\n\n## Pre-launch Checklist\n\n- [X] I read the [Contributor Guide] and followed the process outlined\nthere for submitting PRs.\n- [X] I read the [AI contribution guidelines] and understand my\nresponsibilities, or I am not using AI tools.\n- [X] I read the [Tree Hygiene] wiki page, which explains my\nresponsibilities.\n- [X] I read and followed the [Flutter Style Guide], including [Features\nwe expect every widget to implement].\n- [X] I signed the [CLA].\n- [X] I listed at least one issue that this PR fixes in the description\nabove.\n- [X] I updated/added relevant documentation (doc comments with `///`).\n- [X] I added new tests to check the change I am making, or this PR is\n[test-exempt].\n- [X] I followed the [breaking change policy] and added [Data Driven\nFixes] where supported.\n- [X] All existing and new tests are passing.\n\nIf you need help, consider asking for advice on the #hackers-new channel\non [Discord].\n\nIf this change needs to override an active code freeze, provide a\ncomment explaining why. The code freeze workflow can be overridden by\ncode reviewers. See pinned issues for any active code freezes with\nguidance.\n\n**Note**: The Flutter team is currently trialing the use of [Gemini Code\nAssist for\nGitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code).\nComments from the `gemini-code-assist` bot should not be taken as\nauthoritative feedback from the Flutter team. If you find its comments\nuseful you can update your code accordingly, but if you are unsure or\ndisagree with the feedback, please feel free to wait for a Flutter team\nmember\u0027s review for guidance on which automated comments should be\naddressed.\n\n\u003c!-- Links --\u003e\n[Contributor Guide]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview\n[AI contribution guidelines]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines\n[Tree Hygiene]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md\n[test-exempt]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests\n[Flutter Style Guide]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md\n[Features we expect every widget to implement]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement\n[CLA]: https://cla.developers.google.com/\n[flutter/tests]: https://github.com/flutter/tests\n[breaking change policy]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes\n[Discord]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md\n[Data Driven Fixes]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cf7dc0badc47e795c32fae597d33401f3cfdd67b",
      "old_mode": 33188,
      "old_path": "engine/src/flutter/shell/platform/darwin/ios/framework/Source/FlutterEngine.mm",
      "new_id": "6c7edcbff0a9a415994058ad62916d038aaabbac",
      "new_mode": 33188,
      "new_path": "engine/src/flutter/shell/platform/darwin/ios/framework/Source/FlutterEngine.mm"
    },
    {
      "type": "modify",
      "old_id": "60d78fe1efaacac5d8ec33ca1e8f8714df567874",
      "old_mode": 33188,
      "old_path": "engine/src/flutter/shell/platform/darwin/ios/framework/Source/FlutterEngineTest.mm",
      "new_id": "6bf47196d00e37473fe36ed6a14087153cd94469",
      "new_mode": 33188,
      "new_path": "engine/src/flutter/shell/platform/darwin/ios/framework/Source/FlutterEngineTest.mm"
    }
  ]
}
