Search Issue Tracker
Fixed
Votes
1
Found in
5.5.2p4
Issue ID
898861
Regression
Yes
[IL2CPP][XCode][iOS] Xcode 3 throw error when played (Xcode 8.2.1 does not)
Reproduction Steps:
1. Open User's project
2. Open "Main" scene
3. Run in play mode
4. Notice "Decompressed data length" in console
5. Build to iOS device
6. Open and build on Xcode 8.2.1
7. Notice same message in output field
8. Open and build on Xcode 8.3
8. Notice error message:
ZlibException: inflating:
at Ionic.Zlib.ZlibBaseStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in <filename unknown>:0
at GZipTest.Awake () [0x00000] in <filename unknown>:0
Expected Behaviour: Same behaviour on either of Xcode versions
Actual Result: Xcode 8.3 throw error message when Xcode 8.2.1 does not.
Reproduced on: Xcode 8.2.1, Xcode 8.3
Reprouduced on versions: Unity 5.5.2p4, 5.5.3p1, 5.6.0f3, 2017.1.0b1
Reproduced on devices: iPhone 6 Plus iOS 8.0, iPhone 6 iOS 10.2.1
Comments (3)
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 Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
- Warnings about invalid URIs are thrown when UI Builder's Material field is set to null
- Warnings about invalid URIs are thrown when UI Builder's Variable Asset Reference field is set to null
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
cruelbob
May 23, 2017 10:32
Same problem using BestHTTP with Unity 5.5.3f1 and XCode 8.3.
"inflating: rc=426309664"
Lazybones94
May 05, 2017 12:09
Same issue using DotNetZip on Unity 5.5.2 and 5.6.0 with Xcode 8.3
d4Rk
Apr 25, 2017 06:40
Same issue using BestHTTP which, under the hood, also make use of "Zlib", really annoying.. Took me 2 days to find out, that it's a bug in IL2CPP :/