Approved and product.id #192

chrisschaub · 2015-05-18T23:07:16Z

So, it looks like when the product moves to APPROVED, the product id is no longer intact, it becomes 'application data' -- but from the doc, it seems that the info is stored in product.transaction.product_id ? But that field of transaction does not exist. The purchase is going through, it's a restore. One other question, should I just use a global "when" to catch updates and switch on status? Or should I use "once" since I'm selling NON_CONSUMABLE?

butlimous · 2015-05-18T23:13:15Z

What do you get when you log "product"? not product.transaction . In my case the product ID and everything is intact but the receipt is missing so I can't verify that authenticity of the purchase

chrisschaub · 2015-05-18T23:17:58Z

My product is very funky -- all the data is wiped. The product id is
swapped for "application data". I'm trying to figure out if it's because
i'm using WHEN with NON_CONSUMABLE.

On Mon, May 18, 2015 at 6:13 PM, butlimous notifications@github.com wrote:

What do you get when you log "product"? not product.transaction . In my
case the product ID and everything is intact but the receipt is missing so
I can't verify that authenticity of the purchase

—
Reply to this email directly or view it on GitHub
#192 (comment)
.

Christopher Schaub
http://chris.schaub.com

butlimous · 2015-05-18T23:19:26Z

No I'm using "when" with nonconsumable and it's not a problem

chrisschaub · 2015-05-18T23:23:49Z

Do you wait to call store.refresh() untill all products are registered?

On Mon, May 18, 2015 at 6:19 PM, butlimous notifications@github.com wrote:

No I'm using "when" with nonconsumable and it's not a problem

—
Reply to this email directly or view it on GitHub
#192 (comment)
.

Christopher Schaub
http://chris.schaub.com

butlimous · 2015-05-19T00:10:04Z

Yes the correct sequence is like this:

store.register({id: 'first', type: store.xxxx});
store.register({id: 'second', type: store.xxxx});
store.refresh();

store.when('first', 'updated', function(product) { });
store.when('second', 'updated', function(product) { });

This is the sequence I'm using and It works well.

butlimous · 2015-05-19T00:12:49Z

Are you sure you have setup the WHOLE environment in iOS correctly? It's more tricky than that of Android.

chrisschaub · 2015-05-19T01:17:01Z

I think so. If I've registered products and have a store ready, should I
re-register and declare when's every time the page is drawn? It's an app,
so the store object is just around. Wondering if store.off on leaving the
view is a good idea since it's an angular / ionic app.

On Mon, May 18, 2015 at 7:12 PM, butlimous notifications@github.com wrote:

Are you sure you have setup the WHOLE environment in iOS correctly? It's
more tricky than that of Android.

—
Reply to this email directly or view it on GitHub
#192 (comment)
.

Christopher Schaub
http://chris.schaub.com

butlimous · 2015-05-19T01:19:06Z

Is the state of the product(s) valid or invalid?

chrisschaub · 2015-05-19T01:20:37Z

Valid.

On Mon, May 18, 2015 at 8:19 PM, butlimous notifications@github.com wrote:

Is the state of the product(s) valid or invalid?

—
Reply to this email directly or view it on GitHub
#192 (comment)
.

Christopher Schaub
http://chris.schaub.com

butlimous · 2015-05-19T10:48:32Z

In this case I don't really know what's wrong...As long as the product is valid and the confirm purchase is showing the correct price, the approve state should also show the same info. May it's a bug in ionic as I use phonegap

chrisschaub · 2015-05-19T10:55:59Z

Thanks, I got it working much better by messing with bundle ids. Is it
calling store.finish() that moves it from APPROVED back to VALID?

On Tue, May 19, 2015 at 5:48 AM, butlimous notifications@github.com wrote:

In this case I don't really know what's wrong...As long as the product is
valid and the confirm purchase is showing the correct price, the approve
state should also show the same info. May it's a bug in ionic as I use
phonegap

—
Reply to this email directly or view it on GitHub
#192 (comment)
.

Christopher Schaub
http://chris.schaub.com

chrisschaub · 2015-05-19T10:56:14Z

sorry, calling product.finish()

On Tue, May 19, 2015 at 5:55 AM, Christopher Schaub chris@schaub.com
wrote:

Thanks, I got it working much better by messing with bundle ids. Is it
calling store.finish() that moves it from APPROVED back to VALID?

On Tue, May 19, 2015 at 5:48 AM, butlimous notifications@github.com
wrote:

In this case I don't really know what's wrong...As long as the product is
valid and the confirm purchase is showing the correct price, the approve
state should also show the same info. May it's a bug in ionic as I use
phonegap

—
Reply to this email directly or view it on GitHub
#192 (comment)
.

Christopher Schaub
http://chris.schaub.com

Christopher Schaub
http://chris.schaub.com

chrisschaub · 2015-05-19T14:29:11Z

So maybe it's this. On Android, do I need to use MANAGED instead of
NON_CONSUMABLE for type?

On Tue, May 19, 2015 at 5:56 AM, Christopher Schaub chris@schaub.com
wrote:

sorry, calling product.finish()

On Tue, May 19, 2015 at 5:55 AM, Christopher Schaub chris@schaub.com
wrote:

Thanks, I got it working much better by messing with bundle ids. Is it
calling store.finish() that moves it from APPROVED back to VALID?

On Tue, May 19, 2015 at 5:48 AM, butlimous notifications@github.com
wrote:

In this case I don't really know what's wrong...As long as the product
is valid and the confirm purchase is showing the correct price, the approve
state should also show the same info. May it's a bug in ionic as I use
phonegap

—
Reply to this email directly or view it on GitHub
#192 (comment)
.

Christopher Schaub
http://chris.schaub.com

Christopher Schaub
http://chris.schaub.com

Christopher Schaub
http://chris.schaub.com

butlimous · 2015-05-19T15:00:30Z

No when creating a product in your Google Play developer account, always shows managed, whether It's consumable or not. Then in your code, write it as usual either CONSUMABLE or NON_CONSUMABLE

chrisschaub · 2015-05-19T22:41:52Z

It's weird, iOS is working fine for the most part. But I can't get products in google to register as valid. I have the same bundle id's, BILLING_ID set during plugin install, store object because register works. But products just stay invalid on android. Is there anything special to registering android product I might be missing? My app is in "alpha" and the build is for release, not debug. I've also made sure the uploaded APK matches the one I'm testing with. Any suggestions are apprciated, and thanks for the previous help as well!

butlimous · 2015-05-19T22:56:41Z

Have you published the app? Remember that the app MUST be published to test the purchase. You can publish the alpha version so that It's not available to public

chrisschaub · 2015-05-29T20:44:52Z

Ok, I've got the plugin working much more smoothly now with my app. But, on ios, sometimes after logging in, I get an approved product with a very strange product id, the id is "application data". And it's weird because the product is somehow registered, valid and then approved -- but I'm not passing any product with that id. So, this reply directly relates to my initial comment. Is it possible that the plugin is somethow adding a pseudo product via a bug into store.products?

RouR · 2015-06-13T19:29:01Z

How to publish publish the alpha version? I uploaded app, turn-on TestFligh, add tester acc, open in device app via TestFligh. I got:

{"id":"application data","alias":"application data","type":"non consumable","state":"approved","title":null,"description":null,"price":null,"currency":null,"loaded":true,"canPurchase":false,"owned":false,"transaction":{"type":"ios-appstore"},"valid":true}

I think follow is mistakes:

id="application data" (instead of my id),
price="null" (instead of setted tier6),
transaction={"type":"ios-appsore"} (where is receipt?)
type="non-consumable" (registered type is store.PAID_SUBSCRIPTION)

MauriceButler · 2015-10-03T08:25:18Z

Was there ever a resolution to the "application data" id issue?

I am having the same problem.

gsfioravanti · 2015-10-28T21:39:01Z

Is there any update to this issue? I'm also getting this.

vinceoralim · 2015-11-19T10:03:07Z

I'm experiencing the same issue.
Details:

in app v3.11.1
one app with only one product on iOS and Android
due to store specifics, my product type is différent : PAID_SUBSCRIPTION on iOS, CONSUMABLE on Android. This is the only difference in the code
in app purchase is globally working fine (app in production, daily purchases...)
occurs only on iOS (runs fine on Android)
first call to store.refresh() is OK
but each following call adds a product (id="application data"...) to the store.products array

This is not a big issue, I end up to prevent further .refresh() calls on iOS.

alexdrel · 2016-01-07T00:21:45Z

+1
I am getting "application data" non consumable of second refresh.

acoard · 2016-01-08T19:26:38Z

I'm also suffering from this problem. I believe it's because of this code:

cordova-plugin-purchase/www/store-ios.js

Lines 1360 to 1368 in b9ab6a7

    
           var p = data.bundleIdentifier ? store.get(data.bundleIdentifier) : null; 
        
           if (!p) { 
        
               p = new store.Product({ 
        
                   id: data.bundleIdentifier || "application data", 
        
                   alias: "application data", 
        
                   type: store.NON_CONSUMABLE 
        
               }); 
        
               store.register(p); 
        
           }

Here's the relevant bit:

if (data) {
    var p = data.bundleIdentifier ? store.get(data.bundleIdentifier) : null;
    if (!p) {
        p = new store.Product({
            id: data.bundleIdentifier || "application data",
            alias: "application data",
            type: store.NON_CONSUMABLE
        });
        store.register(p);
    }
    p.version = data.bundleShortVersion;
    p.transaction = {
        type: "ios-appstore",
        appStoreReceipt: data.appStoreReceipt,
        signature: data.signature
    };
    p.trigger("loaded");
    p.set("state", store.APPROVED);
}

Basically it says, 'if we can't get the bundleIdentifier' (presumably the IAP's name), then create a new one with "application data" as the id, and then register it.

This callback is in the storekit re-refresh event, which is called everytime that refresh() is called. So, that explains why it's adding a new one each time.

edit: In case anyone is wondering, at this time data is a string around ~6,000 characters long. I believe it's base64 encoded, but I'm not positive.

milhad · 2016-02-16T16:26:22Z

I'm having the same issue. On the first run, everything runs OK, but on subsequent runs a lot of "fake" products with id "application data" are getting generated and being pushed into the purchase flow because their state is forced to "approved".
This is causing the validator to run, posting the imaginary transaction to my API for validation, which obviously fails.

I will try to circumvent this by checking for "fake" ids in "approved" event handler, but it is still unknown to me as why it happens in the first place.

acoard · 2016-02-16T20:03:19Z

@milhad I just wanted to help point you in the right direction

I will try to circumvent this by checking for "fake" ids in "approved" event handler, but it is still unknown to me as why it happens in the first place.

I tried this, but wound up having lots of trouble.

Instead what worked for me was writing my event handlers like so:

store.when(SINGLE_REPORT).approved(handleSingleReportApproved);

Essentially, always use store.when("INDIVIDUAL_PRODUCT"). Do NOT get all products. You'll just have to filter them and wind up with headaches. At least that's what happened in my case.

Best of luck!

isayeter · 2016-02-19T14:14:58Z

any update ? the same issue here. why plugin registering a new item as @acoard wrote ?

xgat · 2017-04-29T09:11:37Z

Hi,
it seems the workaround from @acoard is working for me: for each product register callbacks with store.when(<single product id>), do not register callbacks with store.when("product").

stale · 2018-05-11T18:21:45Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

chrisschaub closed this as completed May 27, 2015

chrisschaub reopened this May 29, 2015

j3k0 added the Backlog label May 26, 2016

stale bot added the wontfix label May 11, 2018

stale bot closed this as completed Jun 10, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Approved and product.id #192

Approved and product.id #192

chrisschaub commented May 18, 2015

butlimous commented May 18, 2015

chrisschaub commented May 18, 2015

butlimous commented May 18, 2015

chrisschaub commented May 18, 2015

butlimous commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 19, 2015

chrisschaub commented May 19, 2015

chrisschaub commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 29, 2015

RouR commented Jun 13, 2015

MauriceButler commented Oct 3, 2015

gsfioravanti commented Oct 28, 2015

vinceoralim commented Nov 19, 2015

alexdrel commented Jan 7, 2016

acoard commented Jan 8, 2016

milhad commented Feb 16, 2016

acoard commented Feb 16, 2016

isayeter commented Feb 19, 2016

xgat commented Apr 29, 2017

stale bot commented May 11, 2018

Approved and product.id #192

Approved and product.id #192

Comments

chrisschaub commented May 18, 2015

butlimous commented May 18, 2015

chrisschaub commented May 18, 2015

butlimous commented May 18, 2015

chrisschaub commented May 18, 2015

butlimous commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 19, 2015

chrisschaub commented May 19, 2015

chrisschaub commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 19, 2015

butlimous commented May 19, 2015

chrisschaub commented May 29, 2015

RouR commented Jun 13, 2015

MauriceButler commented Oct 3, 2015

gsfioravanti commented Oct 28, 2015

vinceoralim commented Nov 19, 2015

alexdrel commented Jan 7, 2016

acoard commented Jan 8, 2016

milhad commented Feb 16, 2016

acoard commented Feb 16, 2016

isayeter commented Feb 19, 2016

xgat commented Apr 29, 2017

stale bot commented May 11, 2018