We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello, I am moving to UE5, downloaded latest 2.3.0 version, I have probably found a bug trying to connect to server with Query object.
Assertion failed: Pair != nullptr [File:E:\UE5\Engine\Source\Runtime\Core\Public\Containers\Map.h] [Line: 656] UnrealEditor_SocketIOClient!USIOMessageConvert::JsonObjectToFStringMap() [E:\Projects\sopsb\Plugins\SocketIOClient\Source\SocketIOClient\Private\SIOMessageConvert.cpp:200]
I narrowed my code down to this snippet that causes this error. It seems problem is with string values, other values don't cause crashes.
auto JsonObject = USIOJConvert::MakeJsonObject(); JsonObject->SetStringField("testString", "value"); USIOMessageConvert::JsonObjectToFStringMap(JsonObject);
The text was updated successfully, but these errors were encountered:
I think I found it
SIOMessageConvert.cpp:200 Changing from ParamMap[Pair.Key] = Value->AsString(); to ParamMap.Add(Pair.Key, Value->AsString()); fixed the problem.
ParamMap[Pair.Key] = Value->AsString();
ParamMap.Add(Pair.Key, Value->AsString());
Sorry, something went wrong.
Edit: nvm misread. Thanks for spotting this, If you want to make a pull request, I'll merge it.
Although I do suspect the error is pointing that Pair==nullptr in some instances, maybe a sanity check (Pair!=nullptr barrier) there might help
Fix bug with string fields getnamo#311
6eb5a94
Merge pull request #312 from staskjs/master
3d8f0bd
Fix bug with string fields #311
No branches or pull requests
Hello, I am moving to UE5, downloaded latest 2.3.0 version, I have probably found a bug trying to connect to server with Query object.
I narrowed my code down to this snippet that causes this error. It seems problem is with string values, other values don't cause crashes.
The text was updated successfully, but these errors were encountered: