Susbricibe channel from android app is working some time while not working other time

Are you looking for help?

This is a support forum for reporting issues related to Backendless services. Please note that due to our support policy we cannot provide you help with debugging your code, consulting in regards to any language or third-party library usage. For this kind of questions we recommend using more appropriate forums like Stack Overflow.

In order to suggest you a quality solution, we shall usually ask you to provide the details mentioned below first. Including them into your topic right away helps us to start investigating your issue much faster.

In case you have a suggestion or an idea, the details below are not always required, though still any additional background is welcome.

Backendless Version (3.x / 6.x, Online / Managed / Pro )

5.3.1

Client SDK (REST / Android / Objective-C / Swift / JS )

Android

Application ID

2EC0F009-962A-84DC-FF92-CB845DC17800

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. Subscribe to a channel
  2. A message is published
  3. The device should get the message everytime

Actual Behavior

Please provide a description of what actually happens, working from the same starting point.

Be descriptive: “it doesn’t work” does not describe what the behavior actually is – instead, say “the request returns a 400 error with message XXX”. Copy and paste your logs, and include any URLs.

1.Subscribe to a channel
2. Some time message is revcieved while some time it gives Client: got error {code=0, details={}, message=You don`t have permission to take action on this service ‘messaging’ and this operation ‘subscribe’, subject ‘test13’ is wrong }

Reproducible Test Case

Please provide a simple code that could be run in a new clean app and reproduce the issue.

If the issue is more complex or requires configuration, please provide a link to a project on Github that reproduces the issue.

Hi @Anshul_Mishra,

Several questions to clarify situation:

  1. To which channel you had subscribed when received that error?
  2. Did the channel exist on the moment of subscription?

Regards, Andriy