Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

littfam

macrumors regular
Original poster
Jun 7, 2008
123
0
I've been a paid dev for about 5 months now, and have been learning Obj-C and and at the same time am familiarizing myself with Xcode ect.. etc.. I decided to distribute the ios beta to a couple of my colleagues through my provisioning portal in order to test that process. Last night I realized my beta had expired, and attempted to restore through iTunes to no avail. I attempted the same through Xcode, and was having issues through Xcode as well. As a developer in "training" it didn't take me long to realize that downloading the latest release through my dev account and forcing an update solved the problem. But each device (user) in my distribution portal are not as tech savvy to say the least. and were left in a state of confusion with a dead phone.

1. I assume this is the normal process for updating distributes from beta to release ver.

2. If so, why are "True to life" "baseline" testers having to deal with this process to update as well?
 
IMO most developers have no need to run iOS betas. People who are "not as tech savvy to say the least" should not run iOS betas. Did you tell them that they might lose all their data on their devices?

iOS betas are for developers who know what they're doing and have the need to test their apps on these early previews of iOS, usually on devices that are test devices, not personal devices.
 
Yes I informed them of possible data loss etc. Although I am not as experienced as you may be at all this, I'm just trying to get an answer as to why iTunes will not restore to the release version without a local file present. Or possibly entering a DFU mode.

As to why It would be a disadvantage to allow "real world" users test a project under construction under a pre release, I would like it if you could explain that for me. (actually I believe there might be arguments for or against it) I'm here to learn. Everyone has to start from the beginning.

BTW I'm not just distributing the beta to look cool to my buddies, I'm just testing things to see how they work.

Thanks
 
I had to restore an iPad last night that had the beta expire. If a device is locked and says it will not activate then you can't use the restore button in iTunes. If you do a google search you will find Apple's preferred method of recovery. It involves holding the home button down while you reboot but I don't remember the rest of the steps. Look it up. It might just save your friendships. :)
 
yea i use my old iphone 3GS as a test device and its just annoying to update.


i had the beta 6.0 version and everytime there was an update to the beta i had to download it from the developers site and than update it.


yesterday it wouldnt even work, but for some reason today it did.

yea NEVER use ur PERSONAL device with beta
 
One problem with having general testers using beta OSes is that they may not be upgrading as new betas come out, and thus may be reporting problems against your app that have been resolved by a newer beta.

Since you and your testers had expired betas, we know that you had not kept up with new builds. You should probably redo your testing against the released version.
 
Why couldn't you use Software Update from Settings?





i have no idea, when i try to update it said that my iOS is up to date, but i know it wasn't because i DL'd the beta version.


i dont think iTunes or my device can tell the difference when it checks, but it just gets stuck in activation mode.

and when i did try to just regularly restore it with itunes, it says software version "not compatible"
 
I had to restore an iPad last night that had the beta expire. If a device is locked and says it will not activate then you can't use the restore button in iTunes. If you do a google search you will find Apple's preferred method of recovery. It involves holding the home button down while you reboot but I don't remember the rest of the steps. Look it up. It might just save your friendships. :)

Thanks, tried that scenario and it it would not come out of activation mode. Had to download the release and put it on the desktop to see if iTunes and Xcode could could find it. Clicked restore in itunes and restore was up and running

----------

i have no idea, when i try to update it said that my iOS is up to date, but i know it wasn't because i DL'd the beta version.


i dont think iTunes or my device can tell the difference when it checks, but it just gets stuck in activation mode.

and when i did try to just regularly restore it with itunes, it says software version "not compatible"

This was my problem also.
 
One problem with having general testers using beta OSes is that they may not be upgrading as new betas come out, and thus may be reporting problems against your app that have been resolved by a newer beta.

Since you and your testers had expired betas, we know that you had not kept up with new builds. You should probably redo your testing against the released version.

That makes sense to me. Thanks. I am currently working on an app for my company, and though I'm getting close to releasing it to a couple of employees, at this point it probably won't be released during an OS beta period. That said, I know that there would be one or two "power users" that would be willing to (and would want to) test during a beta period with beta OS, and I could maybe use the other users as a control against the other. I want the real users, using the app in their individual environments, in ways I won't be able to duplicate. That's my plan anyway, and I'll probably end up with more headaches in the end over it, But ??
 
While I understand the desire to be on the bleeding most developers and certainly testers will be most productive working with released tools on a released OS.

I have little enough time to work on my own code and my own bugs. I certainly don't need to spend a lot of time working as an unpaid beta tester for Apple.
 
That said, I know that there would be one or two "power users" that would be willing to (and would want to) test during a beta period with beta OS, and I could maybe use the other users as a control against the other.

Yes, that's a good way to make sure you work with the new OS while limiting the the risks. Just remember that you may need to ride herd on people to make sure they do upgrades, and you might spend extra time to diagnose things that are glitches in the release rather than your code.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.