You can put everything in the same package, and make the service runs in a different process by specifying the "android:process" attribute for the service in your manifest.
On Thu, Mar 5, 2009 at 3:01 PM, Mike Collins <[email protected]> wrote: > > The Android Market appears to only support "applications" that are a > single APK. > I've asked over there if this is not the case and Google says making > it a single > APK is the answer. > > We have an application that has a long-lived background service and a > user interface > application, in two distinct processes. Development is done with > Eclipse as two > distinct project/packages yeilding two APKs that are installed. This > works just fine, > except that the Market doesn't support it. > > I've mushed the two projects together into one which yeilds one APK > with the > service marked as run in a separate process. This functions properly > and the service > remains running without the UI. However I am unable to debug in the > service since > the process is not visible to me. > > Not being able to debug the major part of the code is not condusive to > producing > substantive applications. Having to develop the code as distinct > projects and then > when complete mush it together and hope for the best is not good > engineering. > > Flipping the "remote" switch in the manifest for the service is not > very viable since a > lot of code that will run correctly as a single process will fault > when split and without > being able to debug into both process finding these is going to be > very painful. > > Am I missing something? > > tia, > mike > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
