Search Issue Tracker
Third Party Issue
Votes
0
Found in
2020.3
2021.2
2021.2.7f1
2022.1
2022.2
Issue ID
1396558
Regression
No
[Android][UAAL] Unity Built into Xamarin Project causes crash due to a signals mismatch
Reproduction steps:
1. Download user's attached project "SignalCollisionTest.zip"
2. Open and build "XamarinAndroidEmbedUnityTest.sln" normally with VS or Rider IDE, make sure to build the 'XamarinAndroidEmbedUnityBinding' part first
3. Run the app, tap first the "Start Unity" button, wait for Unity part to load, then tap "Trigger GC" button to make Xamarin GC alive and observe the crash
Expected result: Unity Built into Xamarin Project does not cause a crash due to a signals mismatch
Actual result: Unity Built into Xamarin Project causes crash due to a signals mismatch
Reproduces on: 2019.4.36f1, 2020.3.27f1, 2021.2.9f1, 2022.1.0b9, 2022.2.0a5
Reproducible with these devices:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Notes:
-For more in-depth steps check "README.md" in the project folder
-Attached logcat "logcat_unity_signal_crash.txt"
-Issue manifests with any scripting backend (il2cpp/mono) and any version of Unity the Customer has tried (2019.x till 2021.2.x)
-Customer noted that it's constantly reproducible with a 32bit tablet
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
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
Resolution Note:
Unity as a Library does not have official support for Xamarin.
Xamarin is Mono, so a clash with Unitys mono is no surprise, nor is with il2cpp, which is based on mono.