I cannot access the Mac Developer resources this morning.
With a company as advannced as Apple, I would expect them to be able to roll out web updates
seamlessly.
I don't like being out in the cold.
I want to download the Mavericks Beta.
This is what happens in the real world. Get used to it.
I hope you get your app up and running in time; see if you can get an extension to due extenuating circumstances beyond your control. It can't hurt to ask. All they can do is say no.
I have the same issue here. This is an amazing bad behaviour of part of apple.
Apple Developer Update: Aug 5, 2013
We sincerely appreciate your patience as we work to bring our developer program services back online, and we want to give you an update on our progress. The majority of our developer services are currently online, including Certificates, Identifiers & Profiles, Dev Centers, software downloads, Videos, Apple Developer Forums, iTunes Connect, Bug Reporter, App Store Resource Center, and access to pre-release documentation.
We plan to reinstate most of the remaining services this week: Xcode automatic configuration as well as access to license agreements, TSIs, program enrollments, and renewals in Member Center. You can check the availability of these systems on our status page.
As a reminder, if your membership was set to expire during this downtime, it has been extended and your apps will remain on the App Store and Mac App Store.
We apologize for the significant inconvenience that our downtime has caused and encourage you to reach out to our support team if you need any assistance.
Apple's new Developer Center System Status
page should be updated as the remaining services come back online.
Mainstream media may not be reporting on the outage but Google it and quite a few tech blogs have reported on it.
Michael, I'm not sure of your particular circumstances, but if your livelihood was tied into developing new products for apple then you would perhaps have more empathy for the other people who are expressing their frustration? Certainly it is an unusual lack of service for a company that was known for quality. It would be nice if you could try and spend your time more productively that simply refuting every expression of disappointment posted.
" It would be nice if you could try and spend your time more productively that simply refuting every expression of disappointment posted."
I don't refute every expression of disappointment posted; just the more ridiculous ones.
Don't put words into my mouth, thank you very much.
I suppose most, if not all, of you will be downloading everything you can to finish your projects in case the site goes down again. I sure hope so. There are those that did so are diligently working instead of complaining. I know there are certain things that can't be downloaded but all that can be, should be. Also, keep membership payments up to date instead of waiting to the last minute. I know some can't but I think the majority can. It's called saving butt before **** hits the fan as in this outage.
I hear you on the platform-neutral tools approach, D_G.
All 3 platforms (Apple, Google and Microsoft) support C++ development, and if you have code that does more than frob the GUI, time spent developing and debugging that code in another IDE can be amortized by its portability. Last year I developed a private app this way: developed the core code in Visual Studio, and the wrapped it in the Objective C that is mandatory to provide the GUI on an Apple device.
There are a few other lessons I learned from this outage:
Renew your certificates at half their lifetime, rather than waiting for them to near expiration. Some of the representatives of contract houses that spoke here are probably doing this more to handle their stable of developers than to reduce the impact of extended outages, but it serves well for both applications.
Renew your developer's subscription at the first reminder. Apple reminded me a month before it was ended, and that is probably enough time.
Make sure that you have a number of devices provisioned at all times for development. They don't all have to be yours, but they all have to have cloud-backed and restorable. You don't want to get into the situation where you need to provision a device when the portal is unavailable.
Remember that Apple owes you nothing. You have entered into a binding contract with Apple that allows them to refuse you the privilege of having your app sell in their store, and even to force you to engage a third party to audit your machine, on Apple's behalf. You have consented to binding arbitration in the event of any disagreement. When your role and Apple's role are examined, you see that the burden of obligation is primarily on you, the developer.
When major shakeups occur, try to remain emotionally centered. The chaos that Apple experiences during a shakeup will spill over into your life, and you have to manage your response to be happy and useful. Apple's behavior to this "hacking incident" has demonstrates a classic Level I response in the Capability Maturity Model. This isn't to say that Apple always has this level of performance on the CMM, but it looks like this is how it is with the developers suite.
There are a few other recommendations that are not as pertinent to this outage, but generally apply:
If you are a grazer in the Apple ecosystem, don't use your personal hardware for professional development. Personal equipment walks around, gets pounded, gets broken, gets stolen, gets wet; and becomes unavailable.
Professional development requires dedicated hardware, and requires both software and hardware backup. If your big old Mac Pro 2.66 and its herd of hard drives goes down, you need to have backup hardware right now. You and your clients can't wait for somebody to source you an old graphics card whenever it becomes available.
Thanks for the good thoughts. With Apple hardware as pricey as it is, it is tempting to use personal hardware for development, especially if you aren't well funded and are bootstrapping. As well when you are writing software expected to last many versions, you will want to do thorough testing which in my experience means having at least one each of each model of hardware you are supporting. Two is better if you want to determine whether specific behavior is about a single device, or a class. This is true especially when the hardware is young.
Keeping a bevy of machines takes money and space, and maintenance. That is one of the reasons I try to keep the core code platform neutral, so it can be developed on generic hardware until integration time. I am finding it hard to commit to this kind of investment in a situation where acceptance into an app store has no guarantee. With so much stuff in motion, and windows of opportunity as short as they are.
I still have hopes of success in this arena, but it takes the right idea, timing, and guts.
And the developer portal is down AGAIN...
*** Apple? Seriously???
Please somebody tell me when I can register my UDID for usrng IOS 7?
Since yesterday, I'm trying to upload one application on appstore. The process is blocked on the "Your application is being uploaded".
I suppose this is linked to the current problems of the Apple plateform. Someone has the same problem ?
Edit : Ok, after 45min, my application has been finally uploaded.
How lucky you are.
What I wouldn't do to be you right now. You only had to wait 45 minutes to upload a finished app to the app store, I have to wait 45 days.
We're blocked by the license agreement. Apple says they will fix everything in one week. It was monday since they last updated and its now friday with no new updates.
If it turns monday again and I still can't upload my app i will go crazy. Developers should boycott apple and not upload anything unless we ALL have access. There needs to be solidarity here. It can't be every man for himself.
>>It can't be every man for himself.
We are so screwed ....
In the past I have published an app to figure out how to work with iOS. Then, I have not renewed the annual fee because I did not work for this environment .. A few weeks ago I'm working on a new project that requires a new app under iOS. This project was supposed to start in August .. I want to pay the fee in order to design in the devices (the app requires an intensive use of sensors) but I can not for Apple's fault .. I've already lost nine days (these days in Italy, if there is work, there are no days off).
For me it is already a big damage. I'm losing money (much more than the fee) and if I can not start soon, I will lose the opportunity of this work.
I wrote to Apple but got no answer.
Should I give up forever to design in iOS?
Why is the Apple Mac Developer portal down, and for how long?
