title: Unable to Handle Fatal Exception When Unmarshalling unknown type code
body: <p>The latest update to the Microsoft Health application appears to have broken backwards compatibility with the SDK preview resulting in errors similar to the following for Android development:</p>
  
  <pre><code>04-28 20:02:09.001    8840-9755/org.hackerforhire.msbandlight E/AndroidRuntime﹕ FATAL EXCEPTION: f
      Process: org.hackerforhire.msbandlight, PID: 8840
      java.lang.RuntimeException: Parcel android.os.Parcel@1d1d95f2: Unmarshalling unknown type code 40 at offset 368
              at android.os.Parcel.readValue(Parcel.java:2228)
              at android.os.Parcel.readArrayMapInternal(Parcel.java:2485)
              at android.os.BaseBundle.unparcel(BaseBundle.java:221)
              at android.os.Bundle.getParcelable(Bundle.java:755)
              at com.microsoft.band.f.d(SourceFile:820)
              at com.microsoft.band.f.d(SourceFile:40)
              at com.microsoft.band.f$d.a(SourceFile:892)
              at com.microsoft.band.internal.e$3.handleMessage(SourceFile:137)
              at android.os.Handler.dispatchMessage(Handler.java:102)
              at android.os.Looper.loop(Looper.java:135)
              at com.microsoft.band.internal.e.run(SourceFile:148)
  </code></pre>
  
  <p>I previously assumed this was an issue with ProGuard rules per <a href="https://stackoverflow.com/questions/21342700/proguard-causing-runtimeexception-unmarshalling-unknown-type-code-in-parcelabl">this stack overflow</a>; however, that did not have any impact.</p>
  
  <p>At this point, I'm really looking to see if anyone can suggest a good way to dig into the library JAR and see if there's something I can manually patch to get things working. Is there such a thing or is it best to just hope that Microsoft will release a new SDK soon?</p>
  
  <p>Version information:</p>
  
  <ul>
  <li>Microsoft Health Version: <code>1.3.10427.2</code> </li>
  <li>Microsoft Band SDK Version: <code>1.3.10215.1</code> </li>
  <li>Microsoft Band Firmware Version: <code>10.2.2810.0 09 R</code> </li>
  <li>Android Version: 5.1 (Nexus 6)</li>
  </ul>
  
  <p><strong>UPDATE 2015-04-30:</strong> Confirmed that the newest version of the SDK (<code>1.3.10428.1</code>) resolves this issue.</p>