SocketException in rSDK leads to delayed notifications

[nitesh2599]

Faced this while testing arrive with rSDK in staging.

Steps to reproduce -

• Run arrive using the feat/arrive-sdk branch.
• Override the at_widgets dependencies with feat/events-new-sdk branch of at_widgets.
• Send a share location notification from one atsign to another.

[murali-shris]

@nitesh2599 I am getting dependency issues with feat/events-new-sdk branch of at_widgets. Are the required widgets pointing to trunk branch of at_client_sdk and 3.0.0/trunk version of at_commons, at_utils and at_lookup ?

[murali-shris]

@nitesh2599 issue is fixed and merged to trunk, Please verify

[murali-shris]

@nitesh2599 @kalluriramkumar since this issue is environment specific, let us test with arrive apk/ test build on ios in multiple devices.

[murali-shris]

@nitesh2599 does this issue happen with test flight build of arrive in mobile device ?

[sarika01]

As per @tinashe404 on 24th Sep testing: Arrive - No one received event invites, location sharing didn’t work, app kept refreshing, error messages

As of yesterday, @kalluriramkumar is looking into debugging the issue.

[sitaram-kalluri]

@sarika01: I have debugged the issue using blindtahugejrot staging atsign (atsign which @sachins-geekyants provided), The secondary server of the atsign keeps restarting and hence the SocketException

[ksanty]

Will be resolved through issues @murali-shris can you please tag here? TY!