[Unity 2018.3.2f1] Remote Settings crash on GetX

Started getting weird crashes randomly in editor:

Code (CSharp):

1. ========== OUTPUTTING STACK TRACE ==================
2. 0x0000000140AC68F2 (Unity) std::_Tree<std::_Tmap_traits<core::basic_string<char,core::StringStorageDefault<char> >,MemoryFileSystem::Node  __ptr64,std::less<core::basic_string<char,core::StringStorageDefault<char> > >,stl_allocator<std::pair<core::basic_string<char,core::StringStorageDefault<char> > const ,MemoryFileSystem::Node  __ptr64>,56,16>,0> >::_Lbound<core::basic_string<char,core::StringStorageDefault<char> > >
3. 0x0000000141D687E5 (Unity) UnityEngine::Analytics::ConfigSettingsMap::GetValue
4. 0x0000000141D6811E (Unity) UnityEngine::Analytics::ConfigSettingsMap::GetInt64
5. 0x0000000141D87C98 (Unity) UnityEngine::Analytics::RemoteConfigSettings::GetInt64
6. 0x000000014167806A (Unity) RemoteSettings_CUSTOM_GetLong
7. 0x000000001BC32417 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.RemoteSettings:GetLong (string,long)

Value is set correctly in the Remote Settings to the number. Does anyone know what can be causing this?

 

Also, this seems to be all properties related, as it also crashes on GetInt

Code (CSharp):

1. 0x0000000140AC68F2 (Unity) std::_Tree<std::_Tmap_traits<core::basic_string<char,core::StringStorageDefault<char> >,MemoryFileSystem::Node * __ptr64,std::less<core::basic_string<char,core::StringStorageDefault<char> > >,stl_allocator<std::pair<core::basic_string<char,core::StringStorageDefault<char> > const ,MemoryFileSystem::Node * __ptr64>,56,16>,0> >::_Lbound<core::basic_string<char,core::StringStorageDefault<char> > >
2. 0x0000000141D687E5 (Unity) UnityEngine::Analytics::ConfigSettingsMap::GetValue
3. 0x0000000141D6814E (Unity) UnityEngine::Analytics::ConfigSettingsMap::GetInt
4. 0x0000000141D87D18 (Unity) UnityEngine::Analytics::RemoteConfigSettings::GetInt
5. 0x0000000141677D29 (Unity) RemoteSettings_CUSTOM_GetInt

Remote Settings has some connectivity issues as well right now, maybe some technical difficulties?

 

Bump, still crashes. Anyone?
@JeffDUnity3D

 

We identified the issue, and the fix should be rolled out soon. Sorry for the inconvenience.