TYPO3 Core

I now have searched over 4 hours to find a hint, to find a switch you can use to repair that issue. Sorry, I'm out now.

Nothing works:

• Cookie: strict -> lax
• Safari: Website Settings: Deactivate Content Blocker
• Disable IPv6 on Mac
• Safari: Deactivate all Safari Extensions
• Safari: Disable IP Tracking
• Safari: Disable overall website tracking
• Safari: Deactivate privacy tracking for advertising
• Safari: Clear all caches
• Update to most current version of Ventura, Safari and XCode
• Network: Switch from RJ45 to W-LAN
• Renew DHCP Lease
• Unset BE:HTTP
• Activate BE:lockSSL
• Switch from Debug to Production mode
• Problem is the same with PHP 8.1 and PHP 8.2
• It can't be a problem wit DDEV, as customer has the same problem with a server from Mittwald
• I can't find any problem with the SSL certificate

Next topic: Try to analyze the error log of my Mac

• It has something to do with the launchd service
• The problem is somewhere in the WebKit component
• EXC_BAD_ACCESS (SIGSEGV): Is an indication, that a service tries to access a RAM area which it is not allowed to.
• Code 0x0000000000000042 is different from 0x1c6a2628c which confirms the violation
• Last process which throws the exception has Code 0x1c6a2628c. This code is between 0x1c59e7000 - 0x1c70eefff which relates to: com.apple.JavaScriptCore (18615) <296c4d4b-246e-38db-99c4-b3de1a1352de> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
• The Exception was thrown in this method: JSC::AbstractModuleRecord::resolveExportImpl(JSC::JSGlobalObject*, JSC::AbstractModuleRecord::ResolveQueryconst&)
• In a special launchd.log protocol I found following warning lines:
  

  denied lookup: name = com.apple.backupd.sandbox.xpc, flags = 0x8, requestor = parsec-fbf[1482], error = 159: Sandbox restriction
  denied lookup: name = com.apple.biome.compute.source.user, requestor = contextstored[370], error = 159: Sandbox restriction
  denied lookup: name = com.apple.audio.AudioComponentRegistrar, requestor = com.apple.WebKi[16956], error = 159: Sandbox restriction
  denied lookup: name = com.apple.CoreServices.coreservicesd, flags = 0x9, requestor = com.apple.WebKi[16956], error = 159: Sandbox restriction
  denied lookup: name = com.apple.audio.SandboxHelper, requestor = com.apple.WebKi[16956], error = 159: Sandbox restriction
  denied lookup: name = com.apple.DiskArbitration.diskarbitrationd, flags = 0x9, requestor = com.apple.WebKi[16956], error = 159: Sandbox restriction
  

• I have tried to deactivate the sandbox for safari. No chance.
• I haven't found any further details in /var/log/system
• There should be an additional sandboxd protocol, if you open Console.app with sudo. But I can't find it.

I just found this page: https://www.reddit.com/r/Safari/comments/yk2727/constantly_being_logged_out_of_sites/

After deactivating dev mode in safari it seems to work. For now I can navigate through TYPO3 BE for over 5 minutes now without logout. Wow.

I have done this, but it has not given me any improvement. I still get logged out again and again.

I can confirm this issue. Just tried to edit some content on an up-to-date iPad and get thrown to the login if I close or save an content element.

I can confirm this issue as well on MacOS Ventura 13.3.1, Safari 16.4, TYPO3 v12.4.1

It's not happening in every module for me, but clicking on the module icon for the new "Reactions" and "Webhooks" always triggers it for me, sometimes other modules. Modals are unusable, since the login screen is in there as well. In modals this also happens always

Opening or closing the DevTools makes no difference for me.

I also have this problem and have been able to isolate the cause. Every time I saved a text element, Safari logged me out. I suspected the rte_ckeditor and found out that the problem does not occur if I do not import the EXT:rte_ckeditor/Configuration/RTE/Editor/Plugins.yaml in my configuration.

Addendum: I was able to narrow this down further: the cause lies with importModules: '@typo3/rte-ckeditor/plugin/typo3-link.js'.

For me it is not related to CKeditor, since this happens in modules and modals where CKeditor is not loaded at all