You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the guide for in-app purchases (iap_*.htm files) still use the old way and therefore do not reflect the current implementation.
For example, the guide still implies to use 1 as type for consumable (e.g. in "AGK/AGK Help Generator/AGK Txt/guides/iap_006.htm" ) and ignores subscriptions at all.
As it implies to use type 1, it doesn't show the current consumption process either.
According to “InAppPurchaseAddProductID” help file and source code, InAppPurchaseAddProductID ( szID, 0) (type 0) should be preferred to add the consumable and InAppPurchaseResetPurchase( token ) to consume it.
Even if the old instructions in the guide still work, the inconsistency could confuse users and should therefore be adjusted in my opinion.
Another question regarding the iap_*.htm help files: Are there no txt files for these files as there are for the other files?
The text was updated successfully, but these errors were encountered:
Hello,
the guide for in-app purchases (iap_*.htm files) still use the old way and therefore do not reflect the current implementation.
For example, the guide still implies to use 1 as type for consumable (e.g. in "AGK/AGK Help Generator/AGK Txt/guides/iap_006.htm" ) and ignores subscriptions at all.
As it implies to use type 1, it doesn't show the current consumption process either.
According to “InAppPurchaseAddProductID” help file and source code,
InAppPurchaseAddProductID ( szID, 0)
(type 0) should be preferred to add the consumable andInAppPurchaseResetPurchase( token )
to consume it.Even if the old instructions in the guide still work, the inconsistency could confuse users and should therefore be adjusted in my opinion.
Another question regarding the iap_*.htm help files: Are there no txt files for these files as there are for the other files?
The text was updated successfully, but these errors were encountered: