Search Issue Tracker
Won't Fix
Votes
5
Found in
2017.1.0f3
Issue ID
937818
Regression
No
System.DllNotFoundException: MonoPosixHelper is thrown when calling System.IO.Ports.SerialPort constructor on Mobile devices
Reproduction steps:
1) Download and open attached project
2) Build and run "test.unity" scene on an Android device
3) Watch device's logs
-- Notice that System.DllNotFoundException: MonoPosixHelper is thrown (and one line above - unable to find MonoPosixHelper)
Note:
MonoPosixHelper is found inside Editor and Standalone builds (both Windows and Mac)
Reproduced with:
2017.3.0a3, 2017.1.0f3, 5.6.3f1, 5.5.4p2, 5.4.6f1
Devices under testing:
Xiaomi Mi Max, Android 6.0
LG G3, Android 5.0,
Huawei P9, Android 7.0
iPhone 6, iOS 10.3.3
Reproduced on iOS and Android
Resolution: MonoposixHelper is not currently deployed on mobile. We can consider implementing this functionality but have no plans to do so currently.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
SehrStark
Sep 25, 2017 00:37
I have the same issue in MacOS with a standalone build too. (Works fine in editor for me too).
NGC6543
Sep 12, 2017 05:00
I have the same problem with Unity Standalone for macOS.
In the editor it works just fine. Only built app throws the exception.
visualbruno
Sep 10, 2017 06:15
Not fixed in Unity 2017.1.1p1
visualbruno
Sep 03, 2017 18:47
I have the same problem with Unity 2017.1.0p4 and 2017.1.0p5
A workaround is to build with IL2CPP.