We're preloading apps that require specific OEM-level integration. Due to advice in an earlier discussion(http://tinyurl.com/yzpzwgd) we have a model-specific library and our application contains the <uses- library> element in the Manifest to reference this library.
In that earlier discussion Dianne stated that, at some point in the future, the Marketplace would check for that prerequisite prior to displaying an update as being available. I.e. that if we put updates for two handset models (each with a different <uses-library>) that each of those handsets would see the update meant for that model, and none others would see it at all. I would like to know if there's any more clarity as to when this functionality will exist in the Marketplace? Also, do the package names of the differently-targetted applications need to be unique? I also wanted to clarify an assumption based on further questions asked by others in the earlier thread: Will the Marketplace application properly pick up that there is an update available for a preloaded application (assuming they are both signed by the same certificate and use the same package name). -- 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 To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
