The error types exactly match how they are used on iOS. That is, the error type string keys and the reasons they happen exactly match between iOS and Android. So your code for handling these errors should be the same. We try to make it easy on everyone. 
Now, there might be differences in behavior in regards to error alert boxes between iOS and Android. For example, some error types might cause iOS to display an error alert while the equivalent error type on Android might not. I haven’t fully investigated this for myself.
Although I did notice that different version of the Android Marketplace app (before it became Google Play) would display an error alert message for an “invalidClient” while the old Android 2.2 version would not. This inconsistency with Android’s store alone makes me think that the best way to handle errors is to not display an alert message and instead just label the product within the app as “Failed to purchase” and let the user try again. Now that’s just my opinion. Just be aware that for the “invalidClient” error alert on the newest Android devices will give the user the chance to fix it and then continue with the purchase… in which case just wait for the successful “purchase” transaction state to be received.
Anyways, that’s my 2 cents. [import]uid: 32256 topic_id: 24973 reply_id: 103127[/import]