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

Leaked IntentReceiver #17

Closed
JonasVautherin opened this issue Feb 22, 2016 · 6 comments
Closed

Leaked IntentReceiver #17

JonasVautherin opened this issue Feb 22, 2016 · 6 comments

Comments

@JonasVautherin
Copy link

Hello,

When exiting, I receive the following error:

Service has leaked IntentReceiver dji.internal.version.c@4309fc40 that was originally registered here. Are you missing a call to unregisterReceiver()?

It says that the IntentReceiver has been registered somewhere in "initParams", called by "DJISDKManager.initSDKManager()".

Could you tell me which IntentReceiver is registered by "initSDKManager()" and how to unregister it?

Thanks in advance!

@SilverChangjian
Copy link

Thanks for report it. I have recorded in our tracking list. Will provide the result soon.

@JonasVautherin
Copy link
Author

Do you have any news about that?

@JonasVautherin
Copy link
Author

Is it the right place to ask this question?

@SilverChangjian
Copy link

Thanks for your report. That is the aoa accessory receiver. Will fix it in the coming version.

@kenargo
Copy link

kenargo commented Mar 22, 2016

http://forum.dev.dji.com/forum-90-1.html would be better.

In fact this email goes to developers and is quickly turning into a spam overload (IMO).

From: JonasVautherin [mailto:notifications@github.com]
Sent: Monday, March 21, 2016 11:58 PM
To: dji-sdk/Mobile-SDK-Android Mobile-SDK-Android@noreply.github.com
Subject: Re: [Mobile-SDK-Android] Leaked IntentReceiver (#17)

Is it the right place to ask this question?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #17 (comment) https://github.com/notifications/beacon/AM7-OMWTwWdGKX5_h1bE7HoCB8NvlueKks5pv5L2gaJpZM4HfhOK.gif

@talobin
Copy link
Contributor

talobin commented Oct 17, 2017

Will go ahead and close this issue since its been too long.
@JonasVautherin please feel free to reopen if you find version 4.3.2 still has this problem.
Thank you!

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

No branches or pull requests

4 participants