在提交到Apple App Store之前先对Swift代码进行混淆 [英] Obfuscating Swift code before submission to Apple App Store

查看:354
本文介绍了在提交到Apple App Store之前先对Swift代码进行混淆的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我很难找到有关此的任何信息. Android自己将代码混淆处理视为提交到其商店之前要做的事情.但是我从Apple或任何第三方"提交前的清单中都看不到这一点.我可以找到的唯一类似问题是5年前有关Objective-C的问题,而我只能找到1个有关iOS模糊处理的github库.提交给Apple App Store时,混淆Swift代码是否是常见的做法?尤其是要隐藏任何私有API URL或API密钥?苹果是否有Pro-Guard等效产品?

I'm having a hard time finding any info on this. Android themselves mention code obfuscation as something to do before submitting to their store. But I see nothing about this from Apple or from any "third party" before-submission checklists. The only similar question I could find was one 5 years ago about Objective-C, and I only can find 1 github library about iOS obfuscation. Is it a common practice to obfuscate Swift code when submitting to the Apple App Store? Especially to hide any private API URLs or API keys? Is there a Pro-Guard equivalent for Apple?

推荐答案

Java被转换为字节码,可以反编译.

Java gets converted into bytecode, which can be decompiled.

Swift是一种编译语言,而Clang编译器经过高度优化.在发布模式下,它会剥离符号并进行大量优化,这些优化本身就产生了很大的混淆.有用于编译语言的反编译器,但是结果确实很糟糕并且难以阅读.

Swift is a compiled language, and the Clang compiler is highly optimized. In release mode it strips out symbols and does a lot of optimization that does a great deal of obfuscation all by itself. There are decompilers for compiled languages, but the results are really awful and hard to read.

这篇关于在提交到Apple App Store之前先对Swift代码进行混淆的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆