Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No callbacks when using KalturaClientDelegate #6

Open
adeelmiraj opened this issue Jun 27, 2018 · 1 comment
Open

No callbacks when using KalturaClientDelegate #6

adeelmiraj opened this issue Jun 27, 2018 · 1 comment

Comments

@adeelmiraj
Copy link

In my project I have to make multiple calls to my Kaltura Server and those calls cannot be synchronous as it would damage the user experience. Now the issue is when I use the Singleton design pattern the KalturaClientDelegate works as expected. But I use a separate KalturaClient instance for some server calls. In those cases I do not get any delegate method callbacks.

Here are some notable points that may help understand the problem:

  1. Synchronous calls always work
  2. Asynchronous calls (aka KalturaClientDelegate mehods) work if I use KalturaClient in a singleton object
  3. If I create a new instance of KalturaClient then the asynchronous calls do not work

The sample code looks like this:

let config = KalturaClientConfiguration.init()
let logger = KalturaNSLogger.init()
config.logger = logger
config.serviceUrl = KalturaBaseURL

let client = KalturaClient.init(config: config)
client?.ks = KalturaSessionToken
client?.delegate = self

let categoryList = client?.category.list()
print(categoryList.totalCount)

If I comment out the client?.delegate = self line then I receive the response.

Here's the implementation of the delegate protocol.

func requestFinished(_ aClient: KalturaClientBase!, withResult result: Any!) {
    print(result)
}

func requestFailed(_ aClient: KalturaClientBase!) {
    print(aClient.error.localizedDescription)
}
@kaltura-hooks
Copy link

Hi @adeelmiraj,

Thank for you reporting an issue and helping improve Kaltura!

To get the fastest response time, and help the maintainers review and test your reported issues or suggestions, please ensure that your issue includes the following (please comment with more info if you have not included all this info in your original issue):

  • Is the issue you're experiencing consistent and across platforms? or does it only happens on certain conditions?
    please provide as much details as possible.
  • Which Kaltura deployment you're using: Kaltura SaaS, or self-hosted?
    If self hosted, are you using the RPM or deb install?
  • Packages installed.
    When using RPM, paste the output for:
	# rpm -qa \"kaltura*\"
For deb based systems:
	# dpkg -l \"kaltura-*\"
  • If running a self hosted ENV - provide the MySQL server version used
  • If running a self hosted ENV - is this a single all in 1 server or a cluster?
  • If running a self hosted ENV, while making the problematic request, run:
	# tail -f /opt/kaltura/log/*.log /opt/kaltura/log/batch/*.log | grep -A 1 -B 1 --color \"ERR:\|PHP\|trace\|CRIT\|\[error\]\"

and paste the output.

  • When relevant, provide any screenshots or screen recordings showing the issue you're experiencing.

For general troubleshooting see:
https://github.com/kaltura/platform-install-packages/blob/Jupiter-10.13.0/doc/kaltura-packages-faq.md#troubleshooting-help

If you only have a general question rather than a bug report, please close this issue and post at:
http://forum.kaltura.org

Thank you in advance,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants