Im working with a latest version of Xcode on Sierra, as well as with Xcode on another Mac with El Capitan (10.11.6)
iOS SDK works perfect for me, no any major problem. You could face with a minor problems (yellow), but the SDK project should be build despite on it.
What kind of errors you have ?
Thank you for your comment, but as I noted above I'm using Sierra on the Mac. I think others that are using Sierra may have the same error in Xcode?
If you receive a dialogue when you open Xcode and it asked you to update Xcode for new products, this is the one step that corrupted Xcode. The downside is, it doesn't give you an option to back out of the dialogue and still be able to run Xcode. If you're successful in closing the dialog, the next time you open Xcode you will receive the same dialogue that will corrupt Xcode for the FileMaker's SDK. I would really appreciate if anybody has experience with Sierra and this error for the SDK to mention if they have found a workaround?
Another note: if you do a get information about Xcode for version 7, it does not change the version number. The last time this occurred in El Capitan, it changed my version 7 to version 8. I notified FileMaker support about this issue. That is when they told me to only use version 7. The exact quote is, FileMaker and the iOS SDK were designed to use FileMaker with Xcode seven.
I did try to build the application project in Xcode, as it was generating it stopped and presented in error that stopped the simulator from opening the project. If you're using Sierra and El Capitan, did you receive the Apple update dialogue? This appears to be the point at which it corrupts Xcode.
This is becoming more interesting in that when I ran the simulator a couple minutes ago, it now runs the project. All my settings were the same, the project that had 23 errors now loads the simulator correctly. I have to tell you this is frustrating. For the last three days my testing of Xcode produced the same errors. Now for some reason, the simulator started working again? I tried two times yesterday to run the simulator and received the same 23 errors. When I open the application today the project showed the 23 errors! So I highlighted the project, and I started the simulator again, and this time it ran it. It appeared to take an extra long time for the simulator to load the project, but to my relief it now at least will run the simulator. I have a project / projects that I tried several times and they did produce the same error up to yesterday. I guess you can contribute this to standard operating functionality were sometimes things work, and other times they don't work? If someone reads this, in his the same issues I was having please comment back.
Its not really errors, its a warnings.
Could you post it here, I'll try to help ?
You might want to try "AppCode" from Jetbrains.com. It's an alternative IDE (not free), but it might be good as a comparison.
After using rich IDEs full of features (like Intellij IDEA for Java), I avoid XCODE at all costs.
HOPE THIS HELPS.
1 of 1 people found this helpful
Ah, yes, I also saw this errors.
Its because of Apple slightly changed syntax of Swift 3.
You should use the latest iOS SDK 15.0.2
At this point I have 2 projects in work, and as long as they now can use the simulator I will finish them in the current version. Does the new SDK require FM 15 to be used? I am not ready to upgrade to FM 15 it does nothing new for my projects.
As far as I know, you can use v14 database inside iOS SDK 15.0.2 project.
At least it works well for me.
You can use FileMaker 14 with the SDK 15 but I think you need a license for FileMaker 15 to distribute your SDK 15 solution.
Well, maybe we need to wait for FM Go to be updated for iOS 10.
Than for a new iOS SDK for that new version and support for use of Xcode 7 and 8?
Looks like it already supported:
"This software updates FileMaker Go 15.0.1 to version 15.0.2. It addresses iOS 10 compatibility issues and fixes bugs."
Now we need an iOS SDK for that release.