StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13634414
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-29T20:45:29.337
FavoriteCount
0
LastActivityDate
2012-11-29T20:45:29.337
LastEditDate
LastEditorUserId
0
OwnerUserId
1182843
ParentId
11010642
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You should note there are some very misleading errors and dialogs displayed in the demo Dungeons.java: -- If you are getting "Error: This version of the application is not configured for Market billing." You must installed the RELEASE apk to your android DEVICE not emulator meaning: <ul> <li>Exporting your APK and signing it</li> <li>Deleting any previous installation of your app on your device (even debug / developer versions!)</li> <li>Side loading the APK to your device, installing it, and running it.</li> <li>This also means debugging your released app is probably going to be without your debugger attached. If your debugger is attached, do tell me how!</li> </ul> If you are getting "Error: Item not found", there's a decent chance there is nothing wrong. Dungeons.java actually has a bug in it. Let me explain: <pre><code>/** * Called when a button is pressed. */ @Override public void onClick(View v) { if (v == mBuyButton) { if (Consts.DEBUG) { Log.d(TAG, "buying: " + mItemName + " sku: " + mSku); } if (mManagedType != Managed.SUBSCRIPTION && // ** The following line is bug when returns !true which is false, and then makes the if statement false !mBillingService.requestPurchase(mSku, Consts.ITEM_TYPE_INAPP, mPayloadContents)) { showDialog(DIALOG_BILLING_NOT_SUPPORTED_ID); // ** Which then ends up running this else if, meaning it will try to purchase a subscription } else if (!mBillingService.requestPurchase(mSku, Consts.ITEM_TYPE_SUBSCRIPTION, mPayloadContents)) { // Note: mManagedType == Managed.SUBSCRIPTION showDialog(DIALOG_SUBSCRIPTIONS_NOT_SUPPORTED_ID); } } else if (v == mEditPayloadButton) { showPayloadEditDialog(); } else if (v == mEditSubscriptionsButton) { editSubscriptions(); } } </code></pre> Rather it should be written like this: <pre><code>/** * Called when a button is pressed. */ @Override public void onClick(View v) { if (v == mBuyButton) { if (Consts.DEBUG) { Log.d(TAG, "buying: " + mItemName + " sku: " + mSku); } // We need this statement to evaluate to true on a Non-Subscription such as a Managed or Unmanaged Purchase if (mManagedType != Managed.SUBSCRIPTION) { // If the following errors out, show an error dialog. However, it should not make the previous if statement false if( !mBillingService.requestPurchase(mSku, Consts.ITEM_TYPE_INAPP, mPayloadContents)) { showDialog(DIALOG_BILLING_NOT_SUPPORTED_ID); } } // This if statement gets run accidentally without the bug fix, thus trying to buy your "SKU" as a "subscription", which is totally wrong! else if (!mBillingService.requestPurchase(mSku, Consts.ITEM_TYPE_SUBSCRIPTION, mPayloadContents)) { // Note: mManagedType == Managed.SUBSCRIPTION showDialog(DIALOG_SUBSCRIPTIONS_NOT_SUPPORTED_ID); } } else if (v == mEditPayloadButton) { showPayloadEditDialog(); } else if (v == mEditSubscriptionsButton) { editSubscriptions(); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAndroid in-app billing: custom sku purchase gives "Error - item not found"
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USpctj101
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.