Home → Questions →

Managing android developer and production builds

Admin Functions

• Remove

Alvin Fong

17 Apr, 2012 06:59 PM

Hi,

I'm looking for a way to elegantly manage my android project and it's two HockeyApps. As hockeyApp seems to require unique bundle IDs for different apps (I keep a development app and a production app) my current process is having one eclipse project, and renaming the package, hockey-App ID, and shared preferences path, then I generate an APK and smoke test. this takes me 10 minutes or so, a minor inconvenience.

As I understand, my colleague in iOS side has build targets that adds the bundle ID when he creates his dev/pro IPAs, I don't think i have this option.

I'm thinking of possible having 2 eclipse projects with different package IDs, with code synced through SVN or the like. Any advice on what I should do, or any incorrect assumptions I might be holding?

Thanks,
Alvin

1. Support Staff 2 Posted by Thomas Dohmke on 17 Apr, 2012 07:25 PM

   

   Hi Alvin,

   HockeyApp does not need different bundle IDs (i.e. package names) on Android, just the App ID should be different to let crashes and stats run into the right app on HockeyApp. The downside of the same package name for both beta and live app is that Android does not allow to install them in parallel, i.e. you always need to delete the live app before installing the beta app and vis versa.

   One way to go if you want different package names for beta and live versions is to use a custom ant build script. Here is a blog post which described this process for a demo and a full version, but it should work the same way for beta and live builds.

   Please let me know if you have further questions.

   Kind regards,

   Thomas

   Admin Functions

   • Echo
   • Remove

2. 3 Posted by Alvin Fong on 24 Apr, 2012 08:05 PM

   

   Thanks for the reply, Thomas. Eventually I settled on the option of converting my code base to an Android library project with a dev-project and a production-project referencing its JAR. the projects define their own appIDs and package names.

   Admin Functions

   • Split
   • Remove

3. Support Staff 4 Posted by Thomas Dohmke on 24 Apr, 2012 08:09 PM

   

   Hi Alvin,

   thanks for the feedback, sounds like an interesting way to go!

   Cheers,

   Thomas

   Admin Functions

   • Echo
   • Remove

4. Thomas Dohmke closed this discussion on 24 Apr, 2012 08:09 PM.

Comments are currently closed for this discussion. You can start a new one.