Could someone tell me when is this support planned?
By looking at all iOS releases and Unity updates so far I’ve tried to see average time passed between these two, but I miss some Unity release dates (specifically versions 4.6.1 and 4.5.0).
Could someone tell me when is this support planned?
By looking at all iOS releases and Unity updates so far I’ve tried to see average time passed between these two, but I miss some Unity release dates (specifically versions 4.6.1 and 4.5.0).
What kind of iOS 8.2 support are you looking for?
Support for watchKit. Now when I build for ios and try to add watchKit target using Xcode, I get an error, of course.
8.2 Support is also important to me.
With the latest 4.6.2p2 patch release we fixed project append when WatchKit extension is used. Otherwise than that we are not aware about other issues.
Thanks for your reply, however after upgrading to 4.6.2p2, I have created the simplest Unity app imaginable, have switched to the iOS platform, built the app, have opened the project in Xcode and have added the Watchkit target/extension and I receive the following message in Xcode:
error: /Users/rpinglet/Desktop/SimpleApp/Simple/build/Unity-iPhone/Build/Products/ProductName WatchKit Extension.appex: No such file or directory
This should be a very simple thing to do, but it is not. Have you been able to add a Watchkit extension and compile successfully?
Thanks for your help
Now 8.2 is official and new version of Xcode we should make sure all is working correctly.
Hi @
Streamside7
If you have found the solution of your problem can you please guide me too
And i think using Unity 5 , Xcode 6.2 is the best way to implement them. Using Xcode App groups and creating plugin to communicate between the extension and parent app should work fine… Hope this helps…
@Streamside7 have you found the solution, we have the same issue
With the latest Unity patch releases you should not have such problems.
Please submit bugreports.
Thanks!
We’re not using last patch release (4.6.5f1) and we cannot use unity 5 right now. However, I can switch to last 4.6.6p2. Does 4.6 support this ?
Yes. The bug has been fixed in 4.6.6p1.