Instead of having a concatenated string of "description:code" in
AppPurchaseEvent's error code, it'd be easier to split the two into separate
data fields. It's inconvenient to have to parse the string when, based on the
iOS docs, those values are coming in separately anyway.
Original issue reported on code.google.com by dma...@zabustudio.com on 28 Feb 2012 at 2:58
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36923008-error-code?utm_campaign=plugin&utm_content=tracker%2F21979375&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F21979375&utm_medium=issues&utm_source=github).
Original issue reported on code.google.com by
dma...@zabustudio.com
on 28 Feb 2012 at 2:58