How shall we develop apps for the Apple Watch

Question

Created Jul ’15

Replies 5

Boosts 0

Participants 3

How shall we develop apps for the Apple Watch if this bug with launching apps written in Swift has not been fixed in beta 4?

Will we see a hotfixed beta 4.0.1 in the next days? Or shall we switch back to Objective C code and abandon the idea to use Swift for Apple Watch apps? Or can we get an official workaround for this bug?

The time now for testing and finishing our apps is short because we are already in beta 4. I am really thinking if it it is safer to delete the Swift code now and go back to my old Objective C files.

Boost

Answer 1

limtc OP

Jul ’15

I have similar experience. Installed, launched forever.

But a few hours later I tried the app again, it launched! And works!

Maybe it just take a few hours to install, not sure, but this is my experience so far. Yes, I use Swift.

0

Answer 2

Arnfried Griesert OP

Jul ’15

But so you can't test your apps. And this problem was also described here in detail when we were in beta 3.

I will now delete my Swift files from the project and go back to Objective C.

0

Answer 3

limtc OP

Jul ’15

I don't know what's happening or even this is duplicable.

Rewriting all my Swift apps as Objective-C is not an option so I am still testing to see what happened, and at the meantime work on Android Wear.

0

Answer 4

chuckc192000 OP

Jul ’15

I'd use Objective C. It's not going away anytime soon (if ever). Swift is still a work in progress.

0

Answer 5

Arnfried Griesert OP

Jul ’15

I already switched back to my old Objectve C code. Now the Apple Watch can launch the app.

0