Mobile SDK Issue - Video Frames stop being received

MIP
, , ,
1

After some time we stop receiving video frames in NewFrame delegate for VideoPullProxy.

Calling Reconnect() on Video doesn’t help. Calling Stop() and then RequestStream() and .VideoFactory.CreateLiveVideo() with Start() doesn’t fix the problem, the delegate never called with VideoFrame.

Only when we Loginn to Milestone server again and request the stream, using CreateLiveVideo do we start receiving frames again.

What should we do to fix this? We can replicate this by just leaving the app open for a period of time.

This occurs on both ios and android.

2

Hi Josh,

Having in mind the names of the components I will assume you are using Xamarin build of the .NET Mobile SDK.

(Please correct me if I’m wrong).

It is strange that new RequestStream doesn’t help.

You create new VideoPullProxy for it, right ?

Is it reproducible on .NET desktop environment ?

I’ll create an internal issue and will try to reproduce it in house.

3

Btw, did you noticed if it depends on the particular camera.

For example the source resolution of the camera or camera FPS ?

Also does the behavior changes depending on the requested resolution or requested FPS ?

(I’m trying to narrow down the probable reason as well as possibility to reproduce)

4

Josh,

What version of the Mobile SDK are you using?

I’ve searched in our internal bug tracking system and saw that we’ve had similar issue in 12.1 (2018 R1), which was fixed in 12.2 (2018 R2) and 12.3 (2018 R3).

It concerned all the platforms and was reproducible easily.

Another interesting thing is if this is SDK issue or could be a problem in the Mobile server. If it is in the server it should be bale to be reproduced with Milestone Web Client (when web sockets are switched off) or with Milestone Mobile Clients (when Bandwidth optimization is turned off).

5

Petar,

we are using the latest sdk available here: http://download.milestonesys.com/MobileSDK/XPMobileSdk.zip

we have tested against multiple servers, 2017R3 and 2018R3 and we still experience the issues.

it doesn’t appear on any specific camera or framerate.

6

we will test with milestone clients again but so far we haven’t been able to reproduce it on those

7

Thanks Josh,

We are trying to reproduce it in-house, but so far without any success.

8

Hi Josh,

I think we’ve understood the mystery.

The download link you are using contains version 12.1 (2018 R1) of the SDK.

Therefore you experience the issue, but we do not on the latest :slight_smile:

I’ve made sub-folders on the FTP server for different releases.

You can download the 2018 R3 version from:

http://download.milestonesys.com/MobileSDK/2018R3/

Or you can browse the parent directory and choice whatever you need:

http://download.milestonesys.com/MobileSDK/

This is not the official place where those can be downloaded, but will work for you right now.

I’m trying to sync with my colleagues where is the “official” download location, cause I do not see the SDKs on the corporate one (https://www.milestonesys.com/support/resources/download-software)

9

It seems that the official place for downloads of the Mobile SDK is the forum itself.

Going on to the “https://www.milestonesys.com/my-milestone/msp/mip-sdk/” you can find the link to the latest “Download MIP SDK Mobile 2018 R3”, which actually redirects again to the FTP server:

“http://download.milestonesys.com/MobileSDK/XPMobileSdk_2018R3.zip”

10

Petar, thanks for the update. we will test this asap and get back to you.

11

Petar,

we have tried the latest files and it is still NOT fixing our issue. Please advise!

12

Petar, please advise what the next steps are…

13

Hi Josh,

We are trying to reproduce it in-house - so far without any success.

Is it reproducible with the Xamarin sample provided by the Mobile SDK ?

Is it happen on emulator or on real device ?

14

Petar,

We are trying to run the sample: MobileSDKXamarinSample.Android (which is in DotNet\Samples folder in archive)

and we get this error:

Error MSB3073: command exit “taskkill /f /im adb.exe” with code 127. (MSB3073) (MobileSDKXamarinSample.Android).

any recommendations?

15

Hi Josh,

We’ve made a post-build event to kill the emulator in order to optimize the builds on the build server.

Because of the specifics on the build implementation of MicroSoft, it doesn’t work when it is put on the regular project post build section (when executed on build server in particular).

And therefore it is made as a “Target” in the .cproj file.

So you can open “MobileSDKXamarinSample.Android.csproj” navigate to

and remove it.

This should help.