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

Re-Write Android Service Architecture. #23

Open
phinfinity opened this issue Mar 11, 2014 · 2 comments
Open

Re-Write Android Service Architecture. #23

phinfinity opened this issue Mar 11, 2014 · 2 comments
Labels

Comments

@phinfinity
Copy link
Collaborator

The current service used is an IntentService for the background service. As it turns out IntentService s are only used for job processing and not for asynchronous callbacks and the like as we are using. very likely this is the cause for the mysterious nullpointerexception being received onHandleIntent(). Possibly someone understand the Android Service architecture and suggest a better way to implement the service management.

@phinfinity phinfinity added the bug label Mar 11, 2014
@amoghbl1
Copy link
Contributor

well, why not use a normal service and use the onStartCommand function to get the calling intent and do the necessary stuff there? It would work the same way as the current IntentService.

@phinfinity
Copy link
Collaborator Author

The first time I read about services I read only about IntentService, so I don't actually know the android service architecture very well myself so can't comment on it without looking it up myself. But very likely what you're suggesting is what we need to implement.

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

No branches or pull requests

2 participants