Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Maybe I'd like to incorporate features/items that are only included with iOS 8's SDK?
Maybe I'd like to ensure that my applications are 100% bug free and ready for iOS 8's launch later this year?

I'll repeat: you're doing it wrong.

1) Apple is not obligated to release any of the features they have announced. They can and have pulled things prior to release (like AirPrint) before. Betting on those features being in the next version of iOS is asking for trouble.

2) I do not know any successful developer who has said "Well, that feature is only available in the next version, so we'll wait for that". Resourceful developers can and have found ways around iOS's shortcomings. If you're letting this stop you from producing a great product, I don't know what to tell you.

As a so called "full time iOS developer", why would you bet that "Apples backwards compatibility is good enough for one version back (at least)" when indeed many applications face minor to major issues when run in iOS 8?

Because that's the experience I've had.

I currently have 6 applications on the store that hook into the A/V APIs to record video so the applications can react to the ambient environment. All of them were originally written for iOS 5, and none of that code has been changed going through to iOS 7. Likewise, not a single one of these applications has ever crashed due to a new iOS version.

I have two audio geared apps that make heavy use of the vDSP framework. Again, apart from updating the GUIs so they were slightly flatter on iOS 7, I haven't had to change anything since they were originally written targeting iOS 5.

And then I've got 3 fairly large OpenGL based games. Two of them hook into the accelerometers, one uses the compass & GPS as well. The one that uses the compass and GPS did need minor tweaks in-between iOS 5 and iOS 6, but those issues didn't cause crashing or anything severely negative (just slightly increased battery consumption).

I dunno where you're getting "when indeed many applications face minor to major issues when run on iOS 8", because that's ******** propagated by ****** programmers. None of my applications have had any kind of issues related to the applications themselves when running on iOS 8- there ARE issues, but those issues are caused by flakey code on Apple's side- not mine.

Hedging my bets on "unreleased features" such as CloudKit and Swift (which are obviously going to be in the final version) is called planning ahead.

Swift?

Why are you writing your application in a completely untested and unproven language when you have Objective C? Is Objective C too complicated for you to figure out? If that's the case, I'd suggest that you find another profession, because sooner or later you're going to have to deal with C in some way if you want to make truly awesome applications (or maybe you don't care about that bit).

-SC
 
1) Apple is not obligated to release any of the features they have announced. They can and have pulled things prior to release (like AirPrint) before. Betting on those features being in the next version of iOS is asking for trouble.

Apple are publicly 'advertising' features like CloudKit and Swift, so my bet is a pretty good bet.
You let me worry about my problems with my applications, thanks.

I dunno where you're getting "when indeed many applications face minor to major issues when run on iOS 8", because that's ******** propagated by ****** programmers.

There are countless threads in this very category of users reporting quirkiness in some apps, all the way to major crashes and bugs in others.
As for myself when I fly I use a popular app called 'AvPlan' (navigational app for pilots) crashes when you try to use it a certain way under iOS 8.

This is not because of "******** propagated by ****** programmers"; rather quite the contrary.

Even you yourself said you updated your apps to iOS 7's new interface design; which is what a great majority of developers did.

Again, apart from updating the GUIs so they were slightly flatter on iOS 7

So I'd be interested to see when you did this. Either during iOS 7's beta phase or after it was released to the public.
As an avid "never use beta SDK's" yourself SC, that'd mean your users would have a degraded experience when they updated their phones last year to iOS 7 when your app wasn't ready.

My applications will be ready for iOS 8 on launch day - I can be 100% confident that no user will experience any issues whatsoever.
It'll include not just features incorporated in iOS 8's SDK, but a variety of other things.
As for an example of a new SDK feature: CloudKit allows me to create a much more seamless experience, by far. Plus load times are down by a second or so.

--

... I get that it's beta and subject to anything and everything including data loss. Duh...the "you should know better" attitude doesn't help anyone learn anything. I'm just trying to have a dialog around the mechanics of iCloud. .
All you people posting "it's your fault" "read the developer policy" "don't develop" blah blah blah, you're doing nothing to positively contribute to this post or answer the OP question.

Exactly.
My first reply in this thread I harmlessly stated that the "you must have a second sole-beta testing device" isn't a fit one, fit all solution.
Apparently by stating that, I've created World War III.
 
I'm a little late here, but here's the definitive answer to the OP's question. Right now enabling IPL will not delete any high resolution photos on your device.

Don't believe me? Just disable IPL and all of the photos that were originally taken on your device will remain (And only the photos that were originally taken on that device will remain). For example, I have an iPhone and an iPad and I've enabled IPL on both devices, so I can see all my photos on both devices. If I disable IPL on one device, then only the photos taken on that device will remain. (And those photos will all be the full res original version and it will be all of the photos... none will be missing).

So, assuming you still have all the original devices that contributed photos to your IPL and you haven't done anythimg to specifically erase those original photos (such as take a backup with photos off, then wipe the device and restore that backup with no photos) then after the iCloud wipe you can re-enable IPL on those devices and they will resync and life is good again.

On the other hand, if you no longer have a device that contributed photos to your IPL or you deleted the original photos from your device, then you have one day left to locate or create a backup of the photos in your IPL before they are gone for good.

(And like the others said, if you don't already have a backup of your photos, this might be a good time to make one even if you are safe from the wipe)
 
Last edited:
I use Dropbox autosync, so regardless if the pictures are in iCloud, they're also in Dropbox at full resolution I think. Double cloud storage.

5GB is free and holds a lot.
 
Not if you're human you can't! Nobody deliberately writes bugs into software, they come from mistakes or unknown functionality.

Exactly, they do indeed come from mistakes or unknown functionality.
The only difference is by using the beta SDK, I have time on my side to control the variables and ensure everything works as it should :)
 
The iCloud Photo Library wipe did not go well, Renabling it today on my iPhone and iPad has shown unsatisfactory results.

Many photos and videos that SHOULD HAVE been purged returned, and in some cases out of order, or missing random photos.

I was fully aware and OK with the data wipe. However I expect it to be performed properly.
 
The iCloud Photo Library wipe did not go well, Renabling it today on my iPhone and iPad has shown unsatisfactory results.

Many photos and videos that SHOULD HAVE been purged returned, and in some cases out of order, or missing random photos.

I was fully aware and OK with the data wipe. However I expect it to be performed properly.

There are a couple of other threads about this here, but we discovered that when you deleted photos from IPL they were never actually deleted from your device... they just didn't appear in IPL anymore. Since you now need to reload all your photos from your device it appears that the formerly 'deleted' photos that never went away will be synced again. I don't know if they will really be deleted in beta 3 or not.

As far as missing photos or out of order photos goes, I don't know about that. I didn't have any issues like that.
 
OP: I wish I could tell you an actual answer to your question, but even with all the ... er ... "suggestions," let's call them, about not running beta software, there's one thing it looks like everyone's missed: using the new iCloud photo management solution is not required if you choose to use iOS 8.

In the future, I'd recommend that, despite needing to run beta software on your main (and only) device, it's probably best not to utilize any features that aren't needed for developing apps.

From one human to another, I wish you the best of luck in saving your photos! :D
 
Well no real surprise...
After upgrade to B3, I still had thumbnails for photos my phone thought were still on iCloud Photo Library but when I try to look at them they are unable to download (since the wipe removed them from iCPL). See screenshot of low-res photo stuck unsuccessfully trying to download the full-size image -- there's an "!" lower right.

I turned off iCPL and then turned it back on and my photos went from 2,000 down to 60 so yep they were lost. Luckily I had a Dropbox backup of all images.
 

Attachments

  • image.jpg
    image.jpg
    155.3 KB · Views: 154
... and I'm just pointing out that the original poster asked for some help, and all you've replied about is how irresponsible he/she is.

I didn't see anything about asking for help. I see a post that poses a question about what the end result will be when the iCloud beta data is wiped.

My mistake for not having hundreds of thousands in venture capital of which I can use to purchase sole-use test devices.

Just as others have indicated, it doesn't take "hundreds of thousands" in venture capital to purchase sole-use test devices. In fact, you don't have to spend any money on a new device at all using one simple method - develop using the currently available SDK. When you are able to afford a second device or the iOS 8 SDK becomes public. Also in your signature already you indicate you have two iOS devices. You can easily set one up to be used as a beta device while the other you continue to use normally.

I'm not here saying that I haven't accepted the risk, of course using beta software I along side most other dev's understand data loss, bugs and extra nasties would be present.
What I'm trying to point out here is how Apple have quickly made this decision leaving us a short window to consolidate and backup data...

Actually Apple gave an ample amount of time. If you're someone like me and you choose to brave forth and have the patience to use a beta OS as your main OS, backups are important. It took me ~5 minutes to back up all the data from iCloud on my iPad. Backing up an iOS device and downloading iCloud data is not a lengthy process. This is an exaggeration. Not to mention this is something that should be prepared for. If you choose to use a beta software and you rely choose to rely on their beta service (CloudKit), this is something that should be expected. It becomes your responsibility and your problem when you choose to make it your sole service/backup. Anytime I made a file in Pages/Keynote for iCloud I specifically made sure I a physical backup stored on my computer so that if it turns out I need that file, I have it. Backing up your iOS device also applies to backing up your beta services.

I'm not looking for sympathy nor am I attempting to be melodramatic.
As a student attending university the little amount of money that I do earn goes to food, petrol, bills, rent etc.
Just because I can't afford a second device, but I want to develop my applications for the next release of iOS through my uni units... doesn't make me a "baby".

The "you should have a second device" solution isn't fit one, fit all.

Not attempting to be doesn't mean you aren't.

Honestly if your financial situation is that low then developing for beta software is not what you need to be focusing on. Instead in your free time use the FREE resources and worry about managing your financial situation. You can go on without having to develop on a beta OS.

Maybe I'd like to incorporate features/items that are only included with iOS 8's SDK?
Maybe I'd like to ensure that my applications are 100% bug free and ready for iOS 8's launch later this year?

Then wait for the SDK to become public. You can add those things into your apps after it becomes available and you have a stable option. Or have a second device, or you can do it on your sole device but you can't blame Apple when they make changes when they even specifically advise in their own policy to not store important data on your device and to use it on a second non-main device. As far as being bug-free, that's 100% impossible no matter what SDK you use at any level.

There are countless threads in this very category of users reporting quirkiness in some apps, all the way to major crashes and bugs in others.
As for myself when I fly I use a popular app called 'AvPlan' (navigational app for pilots) crashes when you try to use it a certain way under iOS 8.

And at the same time, many apps work perfectly under iOS 8. The apps that have minor quirks can even be fixed without even needing to use anything new from the iOS 8 SDK. A simple value change using the current publicly available SDK can even fix problems sometimes. Sometimes even simple beta updates fix problems. Plenty of developers have even fixed iOS 8 compatibility issues.

As an avid "never use beta SDK's" yourself SC, that'd mean your users would have a degraded experience when they updated their phones last year to iOS 7 when your app wasn't ready.

Already an incorrect statement, and the counterpoint has already had more than enough evidence.

Even you yourself said you updated your apps to iOS 7's new interface design; which is what a great majority of developers did.

That didn't require the iOS 7 beta SDK. In fact, several apps released to the app store for iOS 6 that used design elements from iOS 7. All they did was simply replace their graphics with pieces designed to look like iOS 7.

My applications will be ready for iOS 8 on launch day - I can be 100% confident that no user will experience any issues whatsoever.

You can never be 100% confident there will be no issues. This is literally impossible. There can ALWAYS be a bug that you don't notice. It may only even affect a handful of users, but it can still be there, no matter how much you test.

My first reply in this thread I harmlessly stated that the "you must have a second sole-beta testing device" isn't a fit one, fit all solution.
Apparently by stating that, I've created World War III.

Nope. You said that you couldn't afford two iPhones (an iPhone is not the only iOS device to develop on - many developers actually use the iPod touch) and that you were worried about losing your important data. You were informed that you shouldn't store important data on your beta device, and then you promptly launched the entire argument in a somewhat passive-aggressive manner to add.

I'm jumping out of this now. If you wish to push it further go ahead, but you've backed yourself into a wall.

The issue at hand is complete, and the OP has been answered with a solution. The ultimatum was given - Don't store sensitive or important data on your beta device. If you only have one device to do, then keep local backups. You said you accepted the risks yet you didn't prepare and tried to pin it on Apple. Accept the results.
 
Last edited:
Passive-aggressive?!?
You've read your post, right?

I'm not going to bother replying to your post chrf097 when you try to make me look like the town idiot.
Cheers.

Wow... way to support the next generation of developers and designers.
---
My mistake for not having hundreds of thousands in venture capital of which I can use to purchase sole-use test devices

My point stands.

You don't have to reply if you don't want to, it doesn't affect me. My case as been presented.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.