DevExpress
Hammerhead injection is failing after Safari 26 update
What is your Scenario?
Our testcafe tests have stopped working on safari after we updated it to version 26. We can see from console logs that the reason is that Hammerhead injection is failing. We have the latest version of TestCafe and the latest version of Hammerhead. Are there any workarounds for this issue?
What is the Current behavior?
When running the test on Safari 26 we just get a blank white page. In the console we can read that Hammerhead failed to inject some scriopts into Safari
What is the Expected behavior?
Tests should run without problem on all browsers on the device.
What is the public URL of the test page? (attach your complete example)
norlysplay.dk
What is your TestCafe test code?
We haven't changed anything in the test code. The only thing we have changed is that we have updated the Safari version.
Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
TestCafe version
3.7.2
Node.js version
No response
Command-line arguments
testcafe safari --hostname localhost ./Tests/stripe.testcafe/stripe-general.js -T "StripeTest_ClickOnLiveFilmAsset_LiveTvStreamStarts" --user=stofa --browser=safari --os=mac --payscheme=ccb
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response
We appreciate you taking the time to share information about this issue. We reproduced the bug and added this ticket to our internal task queue. We'll update this thread once we have news.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
same issue occurs on firefox after update to version 144- blank page and error in console: Uncaught TypeError: can't access property "utils", window['%hammerhead%'] is undefined
Hi Wombatka, I was able to reproduce the issue in Firefox. It might, however, be a different case from the one seen in Safari, even though the symptoms look similar. I’ll make this ticket the main reference for tracking the Firefox 144 hammerhead injection problem.
