M132: Fix app shim creation on non-stable channel with ad-hoc signing.

This is a reland of commit d972a88a18664b4b33845e3f71a01f7124d5305b,
with a fix for the fuzzer compile failure.

Original change's description:
> [AppShims] Fix app shim creation on non-stable channel with ad-hoc signing.
>
> When adhoc signed app shims are enabled, web_app_shortcut_copier
> is used to copy the generated app shim to its final location.
> The way web_app_shortcut_copier tries to setup a mojo connection
> to the app that launched it relies on base::apple::BaseBundleID to
> return the same value in the browser and helper process. However
> unless a process explicitly sets this value, it will return the
> bundle ID of stable channel. As such breaking creation of app
> shims from anything other than chromium builds or chrome stable.
>
> Fix this by getting the bundle ID from chrome::OuterAppBundle in
> web_app_shortcut_copier; this should return the correct bundle
> as long as we override the framework bundle path correctly (which
> we do).
>
> Bug: 382015346
> Change-Id: I7323261b48070ed1dd7c5169863b409f00f7e60b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6067566
> Reviewed-by: Mark Mentovai <mark@chromium.org>
> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
> Reviewed-by: Mark Rowe <markrowe@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1391280}

(cherry picked from commit 4907a4c7fa5193e259312e16982fecf5982596f3)

Bug: 382015346
Change-Id: I63f298386d6a7b69088ff32bfe31a15636fbb564
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6068586
Commit-Queue: Mark Mentovai <mark@chromium.org>
Auto-Submit: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1392416}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6081385
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/branch-heads/6834@{#1932}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
5 files changed
tree: f551b16bc7e5d317efb3f19707cc4de77d0df5b6
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.