动态iBeacon和手动输入UUID [英] Dynamic iBeacons and Manual Input of UUIDs

问题描述

我正在开发一个从后端服务器检索iBeacon UUID的应用程序，这意味着该应用程序中没有硬编码的UUID，并且这些ID一直在变化.可以在后端更新UUID，该应用将收到一组新的UUID进行监视.

I'm working on an app that retrieves iBeacon UUIDs from a backend server, that means there are no hard-coded UUIDs in the app and these IDs are constantly changing. UUIDs can be updated on the backend and the app will receive a new set of UUIDs to monitor for.

基于此帖子此处 ，Apple拒绝了支持手动输入UUID的应用程序，而且我不确定我的应用程序是否会进入应用商店.

Based on this post here, Apple is rejecting apps that support manual input of UUIDs and I'm not sure if my app is going to make it to the App store.

我想听听您的反馈，如果您已经走过了这条路，或者已经尝试过类似的概念并通过了审核过程.

I would like to hear your feedback if you've gone through this path or have worked on a similar concept and made it through the review process.

推荐答案

我还拒绝了一个应用程序，因为该应用程序允许手动输入ProximityUUID.我对Apple的立场的理解是，这仅适用于传输作为信标，并且允许用户手动输入ProximityUUID以进行检测.他们不希望您使用手动输入的ProximityUUID进行传输的原因是，它允许创建一个简单的黑客工具来欺骗"其他人的信标.

I have also had an app rejected for allowing manual input of ProximityUUIDs. My understanding of Apple's position is that this applies only to transmitting as a beacon, and that it is allowed to have manual user input of ProximityUUIDs for detection purposes. The reason they don't want you to transmit with a manually entered ProximityUUIDs is because it allows creation of an easy hacker tool for "spoofing" other folks' beacons.

也就是说，您的用例仍然不同，因为您是从服务器而不是直接从用户输入获取ProximityUUID.我在AppStore中有几个应用程序可以完全做到这一点，这是一种常见的做法，因此我认为这对您来说不会成为问题.

That said, your use case is different still, because you are getting the ProximityUUIDs from a server, not directly from user input. I have several apps in the AppStore that do exactly this, and it is a common practice, so I don't anticipate it will be a problem for you.

这篇关于动态iBeacon和手动输入UUID的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！