Bug 274331 - Pass invalidation handler to ExtensionProcess::grantCapability
Summary: Pass invalidation handler to ExtensionProcess::grantCapability
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Process Model (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Per Arne Vollan
URL:
Keywords: InRadar
: 274406 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-05-17 13:25 PDT by Per Arne Vollan
Modified: 2024-05-29 15:39 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Per Arne Vollan 2024-05-17 13:25:48 PDT 
We need to pass the assertion invalidation handler to ExtensionProcess::grantCapability.
Comment 1 Per Arne Vollan 2024-05-17 13:26:29 PDT 
<rdar://problem/126825362>
Comment 2 Per Arne Vollan 2024-05-17 14:16:16 PDT 
Pull request: https://github.com/WebKit/WebKit/pull/28731
Comment 3 Alexey Proskuryakov 2024-05-22 10:51:43 PDT 
*** Bug 274406 has been marked as a duplicate of this bug. ***
Comment 4 Frederik Riedel 2024-05-22 13:01:31 PDT 
(In reply to Alexey Proskuryakov from comment #3)
> *** Bug 274406 has been marked as a duplicate of this bug. ***

Thanks for matching with the duplicate reporting, Alexey!

I am running into the same problem (obviously🙃). 
Until there‘s a fix, is there any known workaround?

Thanks a lot!
Comment 5 EWS 2024-05-28 22:30:24 PDT 
Committed 279428@main (11913004d540): <https://commits.webkit.org/279428@main>

Reviewed commits have been landed. Closing PR #28731 and removing active labels.
Comment 6 Frederik Riedel 2024-05-29 15:39:43 PDT 
Great to hear that this has been fixed finally!

Is there any timeline for when this will ship?
I really hope we don’t have to wait for the public iOS 18 release in fall…

Now that the root cause has been identified and fixed, is there any workaround that we can leverage in the meantime? Our users are desperately waiting for me to fix this, and it is very frustrating that there’s nothing I can do so far.