Search Issue Tracker
By Design
Votes
0
Found in
5.5.1p3
Issue ID
900246
Regression
No
[iOS][IL2CPP] log4net throws Errors: log4net:ERROR Exception while reading ConfigurationSettings
Errors appear in the Xcode Console when the project is run on iOS.
Steps to reproduce:
1. Open User's attached project
2. Make sure that Scripting Backend is set to IL2CPP and Api Compatibility Level is .NET 2.0
3. Build for iOS
4. Run via Xcode for iOS device
Result: Errors are thrown:
log4net:ERROR Exception while reading ConfigurationSettings. Check your .config file is well formed XML.
System.Configuration.ConfigurationErrorsException: Type 'System.Configuration.AppSettingsSection, System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' not found.
at System.Configuration.SectionInfo.CreateInstance () [0x00000] in <filename unknown>:0
at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection (System.String configKey) [0x00000] in <filename unknown>:0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x00000] in <filename unknown>:0
at System.Configuration.ConfigurationSettings.get_AppSettings () [0x00000] in <filename unknown>:0
Reproduced with: 2017.1.0b1, 5.6.0f3, 5.5.3f1.
Not reproduced with: 5.4.5f1 (corrupted files).
Tested with: iPhone 6S iOS10.3
Note:
Not reproduced with Android (Samsung Galaxy S6 edge) with IL2CPP.
If Scripting Backend is set to Mono, the issue does not appear.
Comments (1)
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
- Crash on object:runtime_invoke_void__this__ when opening a specific project
- Circle-shaped rendering artefacts visible in Local Volumetric Fog boundaries box in Scene view when Fog Distance is lower than 1
- “Fog Distance” property name and description is unclear in the Inspector window
- Crash with multiple stack traces when using Burst-Compiled Span.Fill()
- Broken compute shaders propagate via the cache server
makahou
Apr 26, 2017 05:07
I have run into this error too. Does anyone have any idea to solve it?