CloudServices/NativeSync: Difference between revisions

== Setup ==

<p><a href="Mobile/Fennec/Android OtherBuildEnvs#Mac_OSX"> Setting up an Android dev environment</a>

<pre class="_fck_mw_lspace">$ANDROID_HOME/tools/android

</pre>

<ul><li> to create:

</li></ul>

<pre class="_fck_mw_lspace">git clone git@github.com:mozilla-services/android-sync.git

</pre>

<p>android-sync has the following dependencies:

</p>

</li></ul>

</li></ul>

<p>sync-crypto relies on Apache commons-codec 1.5, which includes Base32. The Android system libraries include the 8-year-old version 1.2. As a result, sync-crypto is packaged as an assembly jar (aka über jar).

</p>

<pre class="_fck_mw_lspace">git clone https://github.com/rnewman/base64-unstub

git clone https://github.com/rnewman/log-unstub

</p><p>Note that both android-sync and sync-crypto have JUnit 4 tests that run in both Eclipse and Maven.  The subdirectory android-sync/test includes Android JUnit 3 tests for activity and store testing.  This is to avoid the mammoth annoyance of testing in a VM without introducing robolectric.

</p>

<p>The directions at <a href="Fennec/NativeUI"> Building Native Fennec</a> should be correct, specifically <a href="Fennec/NativeUI#How_To_Build"> How To Build</a>.

</p><p>After building Fennec, make the apk.

<p>The apk will be something like <tt>objdir-droid/dist/fennec-12.0a1.en-US.android-arm.apk</tt>.

</p>

<ul><li> Ensure USB debugging is enabled on your Android device: fom the home screen, select <tt>Settings &gt; Applications &gt; Development &gt; USB debugging</tt>.

</li><li> Ensure your Android device is connected to your computer's USB port.

<pre class="_fck_mw_lspace">$ANDROID_HOME/platform-tools/adb install -r objdir-droid/dist/fennec*apk

</pre>

<ul><li> Ensure the emulator is running.

</li><li> Run

<p><span class="fck_mw_template">{{note|You may need to run <tt>adb kill-server; adb start-server</tt> if adb doesn't recognize the emulator.}}</span>

</p>

<pre class="_fck_mw_lspace">$ANDROID_HOME/platform-tools/adb logcat

</pre>

<p>If you want to use Eclipse:

</p>

<p><span class="fck_mw_template">{{note|You may need to set <tt>M2_REPO</tt>; (for example, as described at [http://www.mkyong.com/maven/how-to-configure-m2_repo-variable-in-eclipse-ide/]) to something like <tt>$HOME/.m2/repository</tt>.}}</span>

</p>

<ul><li> First configure the test suite launcher, under <tt>Preferences &gt; Run/Debug &gt; Launching &gt; Default Launchers</tt>.  Set the Debug and Run launchers to <tt>Android JUnit Test Launcher</tt>.

</li><li> Select the <tt>android-sync</tt> project and execute <tt>Run &gt; Run As ... &gt; JUnit Test</tt>.

</li></ul>

<ul><li> Add the <tt>test</tt> subdirectory as a sub-project using <tt>File &gt; Import &gt; Existing project</tt>.

</li></ul>

</p><p>We don't quite follow the <a _fcknotitle="true" href="Fennec/NativeUI/CodingStyle">Fennec/NativeUI/CodingStyle</a>. See also <a href="http://source.android.com/source/code-style.html">the Android coding style</a>.

</p>

<p>To see the current unit test code coverage (using the Maven plugin integrating Cobertura), from the <tt>android-sync</tt> directory run

</p>

</p>

== Troubleshooting ==

<p>Something is wrong with xml resolution. Check your Eclipse console errors in xml files, which will prevent Eclipse from building resource (R) files - resolve them first.

</p><p>Things to try:

</li><li>Project &gt; Clean, then rebuild the project. Alternatively, you can delete the gen/ directory, and Eclipse will rebuild automatically (Project &gt; Build Automatically checked)

</li></ul>

<p>Start an emulator with "-partition-size 2047" as a flag, to set emulator size.

</p>