Bug 274406 – iOS Safari Extensions Script stops working

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: WebKit Extensions

[Frederik Riedel]

Created attachment 471450 [details]
this is how it should look like, but after refreshing the page, my scripts dont receive any callbacks anymore.

Hello!

I, alongside many of my users, have noticed that something has changed with how iOS Safari Extensions work around iOS 17.4(.1?).

Essentially functionality of one sec’s browser extension to shield websites is broken.

This bug is only about the iOS Safari Extension, the macOS version still works.
This is the live version of the app including the extension: 
https://apps.apple.com/de/app/one-sec-screen-time-focus/id1532875441

So far I thought this was a bug, but none of the iOS 17.5 betas, neither the new iOS 17.5.1 bug fix update have reverted that new behavior.

I have created a feedback request including a minimal Xcode project that can reproduces the issue: FB13769055

At some point after refreshing the website, my extension stops working (content script is just not called anymore…).

It would be great to get some feedback if this is either (1) a new expected behavior on mobile safari or (2) a bug.

If (1) applies, it would be great to get some documentation on this, so we can work on a new version incorporating the new limitations.
If (2) applies, it would be great if you could share a workaround.

Thanks a lot and have a nice day!

– Frederik

[Radar WebKit Bug Importer]

<rdar://problem/128408502>

[Ahmad Saleem]

@Frederik - can you share reproducible Xcode project, you are referring? So we can try to reproduce it. Thanks!

[Frederik Riedel]

(In reply to Ahmad Saleem from comment #2)
> @Frederik - can you share reproducible Xcode project, you are referring? So
> we can try to reproduce it. Thanks!

Thanks for the quick follow up and sorry for the confusion!
Xcode project that reproduces the issue is attached to my feedback request / radar under this id: FB13769055

– Frederik

[Alexey Proskuryakov]

This was determined to be a duplicate of bug 274331. Thank you for the report!

*** This bug has been marked as a duplicate of bug 274331 ***

[Frederik Riedel]

(In reply to Alexey Proskuryakov from comment #4)
> This was determined to be a duplicate of bug 274331. Thank you for the
> report!
> 
> *** This bug has been marked as a duplicate of bug 274331 ***

Hey Alexey!

Is there any way I can try to reproduce the issue I had with the updated (potentially fixed) WebKit version?

– Frederik