Background script in the form of a service worker cannot be debugged

Question

Created Oct ’25

Replies 10

Boosts 6

Views 2.0k

Participants 6

If the extension uses manifest v3 and a background script in the form of a service worker, then in Safari it is not possible to open the background script debugging window. If I expand the Developer menu in Safari, there is nothing under Web Extension Background Data (or disappear after click), which is an error. In other browsers (Edge, Chrome, Opera, Firefox) this works correctly.

If I switch the background script back to non-persistent script mode, everything works fine and from the Developer menu and the Web Extension Background Data submenu I am able to open the background script debugging window for the extension. Am I doing something wrong?

Answered by DTS Engineer in 863411022

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports.

Bug Reporting: How and Why? has tips on creating your bug report.

Boost

Answer 1

PerM OP

Oct ’25

I'm experiencing the same thing, Safari version 26.0.1 (21622.1.22.11.15)

Did you find a solution, @spacilv ?

0

Answer 2

Arnaud- OP

Oct ’25

same too.

0

Answer 3

DTS Engineer OP

Apple

Oct ’25

Recommended

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports.

Bug Reporting: How and Why? has tips on creating your bug report.

0

Answer 4

spacilv OP

Nov ’25

Feedback number is: FB20518740

0

Answer 5

elad-LayerX OP

Nov ’25

I'm also experiencing the same issue - FB20897011

0

Answer 6

DTS Engineer OP

Apple

Nov ’25

Thanks for filing some bugs. I checked and they're still being routed to engineering teams. I'll check back later with a status update.

0

Answer 7

imack OP

Nov ’25

This is pretty bad. It prevents meaningful debugging of a safari extension using MV3.

0

Answer 8

elad-LayerX OP

Dec ’25

Any update?

0

Answer 9

DTS Engineer OP

Apple

4d

Hi @elad-LayerX, thank you for filing FB20897011. In the comments there I can see engineering has asked if you are able to reproduce this problem in the most recent update/beta. Please test and update your bug report as soon as possible.

Please continue to test your software in release and pre-release versions of system software made available to you through your developer.apple.com account. When you do, add details about that into your bug report to keep it up to date. Please see https://developer.apple.com/download/.

0

Answer 10

DTS Engineer OP

Apple

4d

@spacilv thank you for filing FB20518740. It is still being routed to the correct team for investigation. I added some comments that I hope will help with that. However, it appears some investigation of this issue has already started in FB20897011.

0