I signed up for an iPhone development program last December hoping to develop an app but got carried away by other projects in my life. Now I get messages from Apple that my developer account is expiring in a week. I will not be able to post anything in the App Store for the next 6 months at least, thus the question -- if I let it expire now, can I renew, say, in summer of the next year? And, will it have any consequences on my apple ID?
PS. I currently do not have any apps in the App Store, nor that I plan on testing my apps on a real device.
Yep, you can renew/reactivate. Went through a similar experience myself.
The answer is no. There no consequences. You can let your apple Dev expire since you don't have any apps and not wanting to test you don't need it for now. When you get ready again apply and get another one.
Related
Right now I don't have a developer account, so I used to install a watch app on Apple watch series 3 using Xcode. In the last few months, I observed that my app is usually uninstalled automatically after some days about one week even I run the app daily.
May I know what is it causes? What's the approach to find out it causes? Is there any solution for this?
It's because you don't have a paid developer account. A paid developer account will allow an app to remain for longer. Currently 90 days when signed/deployed through Test Flight.
I have been looking around for an answer for a specific question but just got hints for it here and there. I want to know when i submit an app for review for the AppStore:
First, how long does the review process usually take? I know that it may vary but just want to have rough estimate if possible
Second, when an app is accepted does it go automatically to the app store or the developer has the control over when to release it there?
Cheers
AF
check out details, which is my recent app on appstore,
It take 1 week for approval , As I remember, it was taken 3 days too once.
Time taken to publish is all in their hand.
App will be publish directly to appstore.
But you can remember the option for publish by you or apple :) at the time of submitting app
From my experience review takes about 2 weeks recently, but it varied from 2 days to about a month in the past.
When you submit an application you have an option - whether to make application available on appstore immediately after it was approved by Apple, or hold it before developer does that manually, so if you did not select that option then Application should be published on Appstore by default. (See pages 75-76 in iTunesConnect Guide (warning - large pdf file here))
With apple's in-app purchase approval system, is it not possible to have new in-app purchase content available every day? I've read in various places that the process typically takes 1-2 days .. sometimes longer. I know the typical answer to this would be to create a back log, but we're working with time-sensitive content and need it to be delivered every day (think newspaper-esk). What's the next best solution other than back logging?
Any ideas?
Use the same in-app purchase identifier for rotating consumables.
It might be against Apple's policies, though it's highly unlikely that your app will be reviewed regularly after it's approved. I recommend checking the developer agreement before you move ahead with this.
Several years later ...
A good way to do this is to submit several in app app purchase items ahead of time via iTunesConnect. I recommend you submit these IAPs at the time of your app submission. If you have any IAPs waiting for review at the time your app is being reviewed, they will also get reviewed at the time.
The background story:
I work for a company that develops and manufactures a commercial product which can have up to 100+ dedicated PC's in a farm.
We only get a handful of new customers per year.
We developed an iPod/iPhone app that lets us send commands to the farm and pull data. Our parent company has major concerns about putting this app on the AppStore. (I really dont know the details of the paranoia, but I know its probably not a winnable battle).
We planned to distribute the App via Ad Hoc using ONE or TWO new iPods each time we sell a "farm". I have just learned that the Ad Hoc distribution expires after 90 days.
The Question:
Are there any alternatives for permanently loading our app onto an iPod Touch or iPhone without going through the App Store?
Our app has absolutely no use to anyone without our other product. We only plan to load this app on a handful of iPods a year. I doubt this matters, but maybe somebody has another solution?
Apple has an an enterprise distribution program, which might allow what you're trying to do. There's also jailbreaking the iPods. That would let you run unsigned code, so you could build your apps without ad-hoc certs.
I know this post has been marked as answered but i am in the same situation so i though i should share what i have experienced.
There is NO legal solution for this. You can't have an app distributed with out the annoying expiry dates.
I have been onto the ADC support and you can't get an extension on the certificates, you can renew for more than 1 year at a time and they have no interest in helping you.
I have clients who will not let the content of their apps hit the app store. There for they are stuck with sending all the devices back to renew certificates (i know you don't need to xcode etc.. to install the certs but try getting end users to do it...).
I am in the luck situation that i can try send the shell of an app to the appstore and then once verified (i.e. once off login - ssl to our server with the device id and a guid password) the app will download all the sensitive content to the phone.
I don't know if this will work for all apps - i.e. loading classes or libraries dynamically but for me it is only the content that is sensitive.
if anyone would like more info i am happy to talk it over, but i haven't tried getting the app through the store yet. I will try soon, so i can keep you posted if you are interested.
cheers
kle
As of September 2010, Apple has removed the 500-employee requirement. Go nuts!
See my post about setting up an Enterprise Program account (which moderators keep trying to close!):
https://stackoverflow.com/questions/1876333/how-long-does-it-take-to-get-an-iphone-app-into-the-app-store-closed
Issues with getting an Enterprise Program account:
-You need 500 employees.
-You can only provide the app to employees.
Make sure you check the detailed terms and conditions of using Ad Hoc distributions to be sure you are allowed to distribute them as you are doing. On the face of it you are probably okay (Apple link here), but worth checking the fine print. I know the Enterprise Program had a lot of fussy fine print, e.g. needing procedures to recover apps from employees when they leave the company, etc.
If you jailbreak the iTouch/iPhone then you can easily disable Apple's code signing checks. You can then build your app and load it onto the device as normal without worrying about expiry or anything else.
The only problem is that jailbreaking on newer batches of the 3GS is not particularly end-user friendly. For something to give to a client I think you would need to stick with the iTouch.
Is it just me or do the provisioning profiles created on the developer portal expire every 2 months? Why is that insanity?
Is there any way to create a provisioning profile that will last for the entire period of the annual subscription?
I have contacted Apple, but they simply did not answer. Is Apple insane?
Provisioning Profiles have shorter lifetimes now, yes.
I don't think Apple is insane, they probably have a good reason for it. Does it jive with what you want out of life? It appears not, but I would think that they have a legitimate reason for wanting to change the limitations and it is not because of a lack of sanity. Besides, Apple would have to be collectively nuts and I don't think that that is the case or even really possible.
It barely takes a moment to renew an expired one, and then each developer on your team has to update as well - and that also barely takes a moment.
Most iPhone app dev cycles probably hover around the 2 month range anyway so this shouldn't be a big deal to most.
So like the guy in that PS3 commercial - gonna file this one under not an issue.