Xcode errors during iOS build
I'm compiling for iOS (iPad, Simulator) and getting the old messages
Reference to 'Point' is ambiguousand 3 other ones. See image below. I am on Xcode 10.2 / Mojave which builds macOS apps great, but not iOS (HISE Master branch v3.0.1, just released).
I saw some previous threads here about iOS and researched my errors on the JUCE forums and found that they have come and gone multiple times during the last 2 years or so. Some JUCE issues for reference: Juce #1, Juce #2.
Here are my latest build errors
I saw that JUCE community have been battling the Xcode changes for many years when it comes to
Reference to Point' is ambiguousmessages. Seems that the
MacTypes.hwas to blame and it seems to be called through the
@Christoph-Hart I am building macOS apps fine, but not iOS apps. Did you fix the "Reference to 'Point' is ambiguous" for macOS? If so, can we do it for iOS as well?
@bthj - I saw your post about successful iOS builds but have questions - how did you solve these issues? (you mention not using the auto-generated Xcode project at
Binaries/Builds/iOS/, so what did you use instead?)
Happy for any solutions!
- macOS Mojave 10.14.6
- Xcode 10.2
- iOS SDK that runs the Simulator is 12.2
- tested Deployment iOS versions: 8.2, 9.0, 9.4 (so far, same errors)
Btw, thanks @Christoph-Hart for making the PKG and EXE releases on the latest Master merges/commits, highly appreciated!
orange last edited by
@andioak Unfortunately, after getting lots of errors for iOS exporting, I gave break for a while with hoping that the issues to be fixed one day...
Christoph Hart last edited by
iOS is not officially supported anymore (I know the website still says so but we'll remove it from there soon with the new website relaunch).
The effort of keeping up with the platform simply doesn't justify the demand and if you can't develop a native iOS app you will be failing in the last development steps with HISE based apps too.
Also the UI performance is sub-par compared to native iOS apps which feels like running on an emulation layer that is poorly written. I spent days trying go get non-trivial UIs to run with more than 5 fps.
It was a fun experiment and if you're willing to get your hands dirty and know how to profile hotspots and know your way around the App Store / Xcode quirks, you can give it a shot, but even I tried to publish an iOS app twice but then quickly gave up.
@Christoph-Hart Okay, I see. Too bad but I see the time-sucking black hole in re-inventing the wheel for you, especially for such a unique computing environment. Already lots of time spend making new features and fixing bugs. Not worth it.