Open dnlwbr opened 4 years ago
Hi @dnlwbr
thanks for creating this issue. I have definitely seen these errors as well, but I am not sure if they came up in my last builds. I'll check as soon as I do the next builds. From the look of it it seems, that these errors originate in the Newtonsoft library.
For some reason the build includes System.Text.Json.dll in the build files, which shouldn't be used in UWP apps anyways. Maybe adding this library to the link.xml file could resolve this issue. I'll check that and will comment here.
Quick update: When building for Android I don't seem to receive this error message.
I am also getting these errors when building for HoloLens. They never broke anything or so... I'll look into it when I have more time, since it is not a blocking issue. -Eric
Hi @EricVoll , I have the errors on Unity 2019.4.13f1c1, I can deploy the app to Hololens2, but no connections established between ROS and App.
I'm a freshman in Unity, so I can not figure out why, but would like to provide more details if you need anything. :)
hi @flymaxty Did you try to deploy the demo app, or did you build a custom app? When you say, that you can't connect to the ROS master: Do you mean, that you literally can't connect to the rosbridge, or "only" that no messages arrive? Maybe something to note for the demo app: The demo app subscribes to the "/clock" topic. Could you make sure on your rosmaster that something publishes clock messages to this topic? Cheers, Eric
Hello @EricVoll
when compiling my Project I receive the following three errors:
So I've tested your example project and unfortunatly I get the same errors. Nevertheless, the building process still completes successfully and it seems to work when deployed to the Hololens. Did you receive these errors as well?
By the way, is there a reason you choose the "Web Socket Sharp" protocol over "Web Socket UWP" in the RosConnector component in your example project? Which one should be prefered? As serializer I chose Newtonsoft_JSON.
Thanks in advance.
Best, Daniel