search

mimiyaari / dashclock

Automatically exported from code.google.com/p/dashclock
0 stars 0 forks source link

When including extensions in 3rd party apps these extensions are no longer updated in DashClock #562

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a service that binds to extensions
2. Keep it running for a while
3. Check for differences

What is the expected output? What do you see instead?
The values in the extension should be updated, they are not and contain their 
old values.

What version of the product are you using?
DashClock Widget, version 1.5

Which device and Android version are you experiencing this issue on?
Nexus 7 (original), Android 4.3

Are you using a custom launcher or ROM? If so, which one? Note that custom
launchers and ROMs are not supported.
Everything stock, not rooted, nothing.

Please provide any additional information below.
The time in the clock updates as expected, I suspect the extensions are 
disconnected when another service connects. I tried disconnecting from the 
extensions and several other strategies, but they do not resolve the problem
This link:
https://www.dropbox.com/s/8pnqeg33s9rw7er/dashclock%20issue.png
contains a screenshot of my app running besides a widget added in apex 
launcher. You'll see the difference in unread e-mail count.

Original issue reported on code.google.com by nick.mar...@gmail.com on 4 Sep 2013 at 12:06

GoogleCodeExporter commented 8 years ago 
Extensions don't currently support multiple hosts. I'll look into this for API 
v3.

Original comment by roman.nurik on 4 Sep 2013 at 4:19

GoogleCodeExporter commented 8 years ago 
Roman, Just wondering what the v3 roadmap or plans regarding this feature looks 
like. We were supporting Dashclock extensions on http://9cards.io but we are 
currently affected by this issue to the point that as soon as we bind to the 
extensions services Dashclock stops receiving updates since our host overtakes 
on the updates. Since this affects only to the private API in the base class a 
fix could be released in order to support multiple hosts on existing extensions 
as a minor version increase without having to wait for v3. This would work for 
all apps that decide to upgrade to the new API and that would transparently 
benefit from having their extensions exposed in other places beside Dashclock. 
Would you consider a PR to fix the host override and perhaps a flag to allow 
3rd party hosts? Thanks for your consideration.

Original comment by raulr...@gmail.com on 22 Mar 2014 at 10:06