我的应用程序被拒绝。它访问“/usr/lib/libpcap.A.dylib”;我可以做什么来避免它?
我向 Mac OSX App Store 提交了一个简单的应用程序,但被拒绝,并给出了以下解释:
“该应用程序正在以下位置创建文件、写入文件或打开读/写访问:
'/usr/ lib/libpcap.A.dylib'"
我使用一些碳代码,例如 FSMountServerVolumeSync 和 FSGetCatalogInfo。
有什么办法可以让我无效吗?
编辑: 它是由 shell 脚本而不是碳引起的: /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I | sed -e 's/^ *SSID: //p' -ed\")"
I submitted a simple app to the Mac OSX App Store, but it was rejected with the following explanation:
"The application is creating files in, writing to, or opening for Read/Write access the following location(s):
'/usr/lib/libpcap.A.dylib'"
I use some carbon code such as FSMountServerVolumeSync and FSGetCatalogInfo.
Is there any way I could void this?
Edit:
It is caused by a shell-script not carbon: /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I | sed -e 's/^ *SSID: //p' -e d\")"
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
由于问题是由于使用
airport
命令行实用程序造成的,如果您的目标是 Mac OS X v10.6+,我建议您使用 CoreWLAN框架获取当前无线接口的SSID:Since the problem is due to using the
airport
command-line utility, if you’re targeting Mac OS X v10.6+ I suggest you use the CoreWLAN framework to obtain the SSID of the current wireless interface:好的,我知道是什么原因导致了这个问题。
我可以使用fs_usage 终端命令来查看文件系统中发生的情况。我使用“sudo fs_usage -w | grep“/usr/lib”
这就是问题:
15:58:03.049 stat64 /usr/lib/libpcap.A.dylib 0.000007 airport
15:58:03.049 open F=4 (R___) /usr/lib/libpcap.A.dylib 0.000020 airport
我使用 shell 脚本来获取活动 WIFI 连接的名称。很明显,机场打开 /usr/lib/libpcap.A.dylib 进行读取,其他库不会像那样打开(否(R__))
编辑:这是我第二个问题的答案,但是获取 SSID 的各种简单解决方案为我消除了所有麻烦;)
OK, I figured out what's causing the problem.
I can use fs_usage terminal command to see what's happening in the filesysytem. I use "sudo fs_usage -w | grep "/usr/lib"
This is the problem:
15:58:03.049 stat64 /usr/lib/libpcap.A.dylib 0.000007 airport
15:58:03.049 open F=4 (R___) /usr/lib/libpcap.A.dylib 0.000020 airport
I use an shell script to get the name of the active WIFI connection. It is obvious that airport opens /usr/lib/libpcap.A.dylib for reading, other libraries are not opened like that (no (R__) )
EDIT: This was the answer to my second question, but Bavarious simple solution to get the SSID eliminates all the hassles for me ;)