I’ve made a fix.
You can find the updated version of the SDK as well as the sample app here.
In short you have to add in your sample code:
...
parent.RunHeartBeat = true;
...
...
child.RunHeartBeat = true;
...
But there was a bug in the SDK itself, so you have to update the reference.
Hello again,
I updated my server to “2022 R1”
now if I want to get stream with connectionID in javaScript, every time I can see a lot of errors such as “NoScaleImages” and so on
Is it possible to share a javaScript example which is use ConnectionId not login for the new version of your product?
Does this prevent you from viewing streams ? Or just pushes a lot of pressure on debug console ?
With the same code, If I change to login type, I can see streams
But with the connectionId, I can’t
But previously, I could see streams in both ways
Now I’m using “MIPSDKMobile_2019R2” for connecting to “server 2022 R1”
If I update mobile SDK to the new version, still I can’t see streams
Yep,
I see your point.
We’ve removed one particular parameter (for those scaled images) from the protocol (in the newer version of the Mobile server).
It seems however, JS SDK hasn’t been updated properly. Exactly in the part “connectWithId”.
We will discuss how to proceed further and will come back to you.
Hi Mohammad,
I made a hotfix of the JS SDK. You can get it from here. Please check if it works for you.
I found another problem:
I’m working with 2022R1, getting connection string for a while, everything is okay.
but after a while, I get one of these 2 errors when I try to get connectionString without any change.
1)“The processing instruction target matching \”[xX][mM][lL]\" is not allowed."
2)I checked this error number, you don’t have this error number in your document and as I can see it looks like some unhandled error becausethe error code gets the default value I guess.
Let me know if u need some logs from the server or …
Is this related in any way to the title of the current forum thread, or to your previous problems?
If not, please open a new thread and ask your question there, providing some context:
- which language/platform (.NET, Javascript, …)
- what are you trying to achieve
- what request do you send
Ideally, only one question per thread should be discussed, and this is the forth one already.