Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.4
MacOS IL2CPP ignores project's Objective-C native source files
Unity supports compiling plugins using native programming languages such as C, Java, and Objective-C. In 2018 MacOS IL2CPP support was added to Unity. Adding C/C++ files to a project results in them being compiled and the code accessible to the csharp layer.
Currently and since at least 2018.4, adding *.m, *.mm Objective-C files to a project makes no impact to a project.
Adding *.m, *.mm Objective-C files to a Unity Project would make the code in those files be compiled, included in executable, and accessible to the csharp layer.
1 Create a Unity project in 2018.4
2 Add a *.m file
3 Add a *.cs file with a binding to that objective-c
5 See csharp be unable to access the objective-c
https://drive.google.com/open?id=1qydRWAo-ur9wDBoaTMWcDgfGGXuzzr0_ (see slack discussion for instructions)
A support-request was opened for the Unity IAP plugin on MacOS IL2CPP due to its inability to utilize the Apple Objective-C StoreKit API.
* Enterprise customer Ninja Kiwi blocked from releasing on MacOS
* ATTN Sebastien Thevenet, John Sietsma
* Project == Bloons TD 6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Shader error db grows on each build
- Android ARCore build fails with 2019.4 due to outdated Gradle
- [tvOS] Visual artifacts are present when Ambient Occlusion is enabled and Dynamic Resolution is reduced
- Texture Importer Inspector throws errors when a built-in texture inspector is overwritten in C#
- Invalid AABB error is thrown when moving a Particle with Velocity over Lifetime and Limit Velocity over Lifetime modules