[Unity 2018.3.2f1] Remote Settings crash on GetX

Unity Services
1

Started getting weird crashes randomly in editor:

========== OUTPUTTING STACK TRACE ==================
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> > >
0x0000000141D687E5 (Unity) UnityEngine::Analytics::ConfigSettingsMap::GetValue
0x0000000141D6811E (Unity) UnityEngine::Analytics::ConfigSettingsMap::GetInt64
0x0000000141D87C98 (Unity) UnityEngine::Analytics::RemoteConfigSettings::GetInt64
0x000000014167806A (Unity) RemoteSettings_CUSTOM_GetLong
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?

2

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

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> > >
0x0000000141D687E5 (Unity) UnityEngine::Analytics::ConfigSettingsMap::GetValue
0x0000000141D6814E (Unity) UnityEngine::Analytics::ConfigSettingsMap::GetInt
0x0000000141D87D18 (Unity) UnityEngine::Analytics::RemoteConfigSettings::GetInt
0x0000000141677D29 (Unity) RemoteSettings_CUSTOM_GetInt

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

3

Bump, still crashes. Anyone?
@JeffDUnity3D

4

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

1 Like