Most of you have probably heard about the issues being written about around apps that use UDIDs. Apple’s policies on the matter are, like everything else, pretty opaque. This is unfortunate, because it creates panic and speculation.
So I want to give you the latest relevant information and our plan to address this.
First of all, we want to make it clear that we have not heard of a single Corona-based app being rejected because of this. In fact, after talking to partners, it is clear that very few, if any, apps have been rejected by Apple specifically because of the use of UDIDs. At the same time, Apple has deprecated the API and we do want to address this before it becomes an issue.
Given that UDIDs have been integral to how most companies have tracked data about consumer app usage, plans on how this will be addressed are still in flux. Any service provider that moves away from UDIDs overnight risks losing continuity between historical and new data. Therefore many companies we have talked to are planning on having an intermediate solution that uses both UDIDs and a new scheme, moving away from UDIDs entirely after some time. This, for example, is the case with Flurry.
As far as Corona is concerned, here’s what we plan to do:
1) Partner SDKs – In Corona we have integrated SDKs from 3 partners that use UDIDs (Flurry, inneractive and Inmobi). We are now in touch with all 3 and they have given us updates on how they are planning to address this issue. We should receive new SDKs from them in the next week or so and we will quickly integrate them into new builds of Corona. As mentioned above, these new SDKs may still use traditional UDIDs (via Apple’s deprecated APIs), but will be preparing the move towards alternatives. We (Ansca) also want to make sure we minimize disruption for our developers, so we will try to bundle these new integrations into as few new builds as possible.
2) LaunchPad Analytics – As part of our analytics we also will be moving away from using deprecated APIs. We are currently finalizing plans for what solution we will use to replace UDIDs. Like with the partner SDKs, we will phase this into our builds sometime in the next 2 weeks. There are several options to replace traditional UDIDs, but they all have different tradeoffs, so we want to make sure we make the right choice.
As part of this plan, we will be introducing these changes into a daily build, and then also making them available in a public release.
I want to reassure you that privacy and your ability to publish apps with Corona are very important to us. We’re working hard on this to ensure there won’t be any issues. And we will be updating as we make progress. Please let us know if you have any questions or concerns.
P.S. next month, I’ll be outlining some of the things we’ll be doing to create more regular stable public release builds. Stay tuned!