iOS App doesn't work in most recent beta

[bicape]

I've been working on an app for the past couple weeks in swift and it's been going great. Realizing that I've been working in beta 4, 2 behind current, I installed beta 6 and now my app has several compiler errors. These errors tend to revolve around unwrapping and the use of 'nil' and 'error'. Unable to find a fix I went back to beta 4 where my app works perfectly.
Should this be a concern for when the stable release of xcode comes out? If necessary am I able to archive in beta 4 and submit via that?

Thanks

 

[JohnsonK]

Things are expected to change while in beta stage, so yes, you have to read Apple's change log and fixes and adjust your code accordingly. You won't be able to submit beta stuff to app store, you will need to wait until final release and go with that

 

[Menel]

I've been working on an app for the past couple weeks in swift and it's been going great. Realizing that I've been working in beta 4, 2 behind current, I installed beta 6 and now my app has several compiler errors. These errors tend to revolve around unwrapping and the use of 'nil' and 'error'. Unable to find a fix I went back to beta 4 where my app works perfectly.

Should this be a concern for when the stable release of xcode comes out? If necessary am I able to archive in beta 4 and submit via that?



Thanks

Yes. I would be concerned. You need to figure out what changed and get that running,

It might be a beta quirk, but since the beta's are specifically for devs to write code... My guess is API code changed, and you need to change to adapt.

Code compiled under beta xcode will not be allowed in app store.

 

[PhoneyDeveloper]

The swift language syntax has changed with every beta. You must make changes to keep up. This is discussed in the release notes and in the Apple swift developer forum.

 

[Dookieman]

The swift language syntax has changed with every beta. You must make changes to keep up. This is discussed in the release notes and in the Apple swift developer forum.

This is the reason I've put off "Learning" Swift. I tried it out once it was released and got a some simple things running, but then they broke. So I'm sticking with Objective C for the forseeable future, I know eventually I'll have to switch, but by then I'm hoping there will be more resources available etc...

 

[JohnsonK]

This is the reason I've put off "Learning" Swift. I tried it out once it was released and got a some simple things running, but then they broke. So I'm sticking with Objective C for the forseeable future, I know eventually I'll have to switch, but by then I'm hoping there will be more resources available etc...

The changes are generally small, don't think they would be reason to ditch swift

 

[Dookieman]

The changes are generally small, don't think they would be reason to ditch swift

I'm not ditching it, I plan a switching to Swift eventually. I just think it's premature to jump on the Swift bandwagon since it still in its infancy.