safari 扩展_为什么构建Safari应用扩展程序是2020年的噩梦

最新推荐文章于 2023-12-19 11:57:03 发布

weixin_26735419

最新推荐文章于 2023-12-19 11:57:03 发布

阅读量607

点赞数

文章标签： python java 小程序 ViewUI

原文链接：https://medium.com/swlh/why-building-safari-app-extensions-is-a-nightmare-in-2020-48cb1a79c8db

版权

safari 扩展

Safari App Extensions is the new way of Apple to develop Safari Extensions along with Cocoa Mac apps. Integrated into the App Extensions environment, it was a logical step to harmonize the ways to extend your Mac apps’ functionalities.

Safari App Extensions是Apple与Cocoa Mac应用程序一起开发Safari Extensions的新方法。集成到App Extensions环境中，这是协调扩展Mac应用程序功能的方法的逻辑步骤。

It came with a promising and innovative tech stack for a browser extension: a Swift/Javascript combination rather than a full Javascript experience.

它带有用于浏览器扩展的有前途和创新技术堆栈：Swift / Javascript组合而不是完整的Javascript体验。

With this in mind, I was pretty excited. I mean: develop for the web with Swift ? This is the best news since the release of Vapor !… Right ?

考虑到这一点，我感到非常兴奋。我的意思是： 使用Swift为网络开发 ？这是自Vapor发布以来最好的消息！

Or so I thought. I decided to give it a shot, and I discovered how unstable the development experience was.

还是我想。我决定试一试，发现开发经验是多么不稳定 。

Why though ? I’ll explain.

为什么呢？我会解释。

调试器突然杀死了您的进程 (The Debugger kills your process abruptly)

Yes, you heard me. While you run the “hello world” example that Xcode provides, after 1 or 3 minutes, Safari closes itself, and so does your extension.

是的，你听到了我的声音。在运行Xcode提供的“ hello world”示例时，在1或3分钟后，Safari会自行关闭，您的扩展也会关闭。

You might think that’s a Safari crash, but that’s in fact a part of the dev process. From what I have seen, the Xcode debugger kills the browser if no interaction/messaging is found during a certain lapse of time.

您可能会认为这是Safari崩溃，但这实际上是开发过程的一部分。据我所知，如果在一定的时间间隔内未发现任何交互/消息，则Xcode调试器将终止浏览器 。

So to avoid this, what you have to do is to write that code inside your injected script :

因此，为避免这种情况，您要做的就是在注入的脚本中编写该代码：

setInterval(() => safari.extension.dispatchMessage("ping", {}), 1000);

This will send a ping to the app every second, just like a keep-alive, begging the debugger not to kill your process. However, this should be done only while debugging and not for production code.

就像保持活动状态一样，这将每秒向应用程序发送一次ping操作，恳求调试器不要杀死您的进程。但是，只能在调试时执行此操作，而不应在生产代码中执行此操作 。

Also, under release configuration, this does not apply, and the Safari App Extension runs without killing the browser.

此外，在发行版配置下，这并不适用，并且Safari App Extension可以运行而不会终止浏览器。

In addition, the docs do not mention this debugger behavior at any time. Well almost, as this archive paper proves that an App Extension can be killed anytime by the system if it takes long to load.

此外，文档在任何时候都不会提及此调试器行为。 差不多了 ，因为这份档案文件证明，只要加载很长时间，应用扩展程序就可以在任何时候被系统杀死。

该扩展有时无法安装到Safari (The extension sometimes fails to install to Safari)

When you’re developing Safari App Extensions, you might run into that error in Xcode’s debug console :

开发Safari应用程序扩展时，您可能会在Xcode的调试控制台中遇到该错误：

Computing the code signing dictionary failed for extension with identifier com.developer.myapp

Computing the code signing dictionary failed for extension with identifier com.developer.myapp

This might happen more often when your extension’s certificate is self-signed.

当扩展的证书是自签名的时，这种情况可能会更经常发生。

To avoid this, you have to:

为避免这种情况，您必须：

Close and quit all instances of Safari
关闭并退出Safari的所有实例
Click Product → Clean build folder
单击产品→ 清理构建文件夹
Run your Cocoa Mac App first by changing the scheme in Xcode’s toolbar.
首先通过更改Xcode工具栏中的方案来运行您的Cocoa Mac App 。
Run the Safari Extension by changing the scheme in Xcode’s toolbar.
通过更改Xcode工具栏中的方案来运行Safari扩展 。

My theory is this happens because self-signed app certificates might expire sooner than Developer Program Certificates. And that’s why we have to rebuild the app almost every time we run the project: to renew the local certificate.

我的理论是发生这种情况，因为自签名应用程序证书可能比开发人员计划证书更早过期。这就是我们几乎在每次运行项目时都必须重建应用程序的原因：更新本地证书。