I would try the following approach: When an update is required, open the built-in web browser and pass an URL to a web site that you set up, and that contains the latest version .apk for download. User clicks on the respective link in the browser, and the download starts. This requires sideloading available and activated. AT&T-issued devices for instance do not allow sideloading. If you publish in Android Market, point to Android Market instead (there's information on this list how that works, too, just go dig for it).
On Nov 23, 1:01 pm, Biosopher <[email protected]> wrote: > We are providing an Android Service to multiple customers for > packaging into their .apks and need to ensure that only a single > instance of our Service is running at a time. The ideal situation > would be this: > > When one of our customers's apps is installed on a device, it looks > for instances of our Service. If our service is not present, our > customer's app would install our Service. If our Service was present, > the customer's app would use the existing Service. If the currently > installed Service was an older version, our customer's app would > upgrade the current Service with the newer one. > > We are pursuing a Shared Library solution, but this introduces many > extra issues: access to resources, declaration of our Services in the > customer manifest, .... Instead, we prefer to provide our customers > with an .apk that would be optionally installed. > > Has anyone tried to do anything similar? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
