Thank you so much for your help so far Ribis!

I understand the principle behind what to do when, and am doing pretty much what you described:

This is my current state:

Short explanation:

I have an Intro Screen.

If you don't have the IAP you get a Pop-Up.

The Pop-Up lets you either choose "still testing" if you are still within the free testing period

or lets you purchase.

Since I know that "has product" returns 0 "on store registration success" even we the user has the product and only returns 1 after some ms, my most recent question is, how do I know how long to wait if the user has the product before triggering the freemium pop-up if not "on store registration success" :P

I could upload my project file but I doubt anyone feels like looking into it, since I don't have like a "minimum version of it", even though everything is kind of well commented and sorted :D

Maybe you see like an obvious mistake from my screenshots?

Have a great week!

Best,

Chris

Hi Ribis,

thank you so much for your help!

I just made a pretty interesting test.

If I do:

Condition: Google Play is loaded

Action: "Add product ID" with type and "Complete product registration

it does fire on every tick (as expected)

BUT if I do:

Condition: Google Play on loaded

Action: same as above

it doesn't fire... I do not understand why.

How is this even possible :D

Regarding my overall problem of my in-app purchases not working:

I think it all comes down to X (inverted) Has product "myIAP_product" is first true and only after a couple of ms turns true if Has product "myIAP_product" is being detected.

Therefor my app starts reacting though the IAP has not been purchased and then gets mixed up when it changes.

I thought when On store registration success fires only one state is returned. Not first 0 then 1.

Has anybody have any experience beyond all this guess work?

Hi Ribis,

I did some more testing.

" it can be quite annoying for someone to wait 2/3 seconds before the game start"

you mean each game? Like each round?

I am pretty sure you only have to sign the user in once the app starts, or when the user loses internet (many people do "on signed out > sign in" in that case).

By using my debug text I was able to further understand the sequence.

Answer to Question 1:

Q: Is "On store registration success" the event that fires "complete product registration"?

Is Store and Product Registration the same?

A: Mobile IAP's documentation seems very confusing on this topic: construct.net/en/make-games/manuals/construct-3/plugin-reference/mobile-iap

"If registration succeeds then On Registration Success triggers."

"Store Registered

True if the registration stage successfully completed."

"Complete product Registration

Ends the registration stage. After this has been called you will no longer be able to register products. This must be called before you can purchase products. On registration success will trigger if successful."

Answer to Question 2:

Q: It seems like "has product" (inverted) is always true at the beginning - aka. does not have product.

"Has product" triggers some time afterward, if true. But it seems not to be "on store registration success".

A: This is true. It indeed seems like "has product" is returning 0 on and some time after "store registration success" fires until "has product" finally returns 1 (if the user has the product).

Answer to Question 3:

Q:(Why) do I actually need the whole Sign in GooglePlay and request player details stuff? Since this is an Android Native Project, aren't the users signed into Google Play anyway? Or is this Google Play sign in this additional Google Play SERVICES thing not the regular Google Play Account sign in?

A: I still don't know.

Do I need "Google Games Services" for Mobile IAP to work? Do I need to configure OAuth for this, really??

Hello dear C3 community,

I have some issues making my IAP work. Therefore I'm doing a lot of tests trying to figure out some questions I have. I would be so happy if anybody could help me with those:

Question 1:

Since it is important to add the IAPs product ID and then "complete product registration" on start of layout - I did so. Now I want to trigger events once this is finished. Is "On store registration success" not the event that fires once "complete product registration" ? (The one being "product-" the other "store registration")

The documentation seems a bit slim on its Mobile IAP page.

I don't understand the whole sequence of Mobile IAP as well.

Question 2:

It seems like "has product" (inverted) is always true at the beginning - aka. does not have product.

"Has product" triggers some time afterwards, if true. But it seems not to be "on store registration success"

My goal...

... is simply to have two possible outcomes of my intro screen.

1. Sign into Google Play Services

2. Setup IAPs using add product ID and Complete product registration

3. Once all this is finished: check if user has product or hasn't

4. Depending on has or hasn't either show freemium pop-up or let the user straight to the main app.

I can't make this work :D

Something like this:

I'ld appreciate any tip, help or advice :)

Have a great weekend!

Chris

PS: Question 3:

(Why) do I actually need the whole Sign in GooglePlay and request player details stuff? Since this is an Android Native Project, aren't the users signed into Google Play anyway? Or is this Google Play sign in this additional Google Play SERVICES thing not the regular Google Play Account sign in?

Hi! Thanks for your reply. Yeah, I read that.

Any idea why it is giving me that clear error message when I build an apk, but not when building a bundle?

This weirdness coupled with the problem that I'm like 99% sure what the password is, since I screenshotted it :D, started me wondering.

Hello,

I'm having trouble understanding my issue before I can even think about posting a bug report. Because I'm pretty sure, it's must be me causing the issue :D

Any help would be greatly appreciated.

All my signed android builds fail when building.

It started when building my last version. So I tried building older versions that I already successfully built and released to the play store. This is all I get when building a "signed android app bundle":

and "signed release apk" and "signed debug apk" give me the following error:

I checked my project settings, plugins and application signing options. Nothing looks fishy to me. And since even ok older versions get the same issue I'm kind of lost.

Anybody here who has an idea?

I gladly share anything you ask for. But I didn't see a reason why my c3 file would help for example.

Best,

Chris

Uh I hear you Windwalker! Thanks for your comment.

Color options in the personalization menu might be a backlog-able thing. I will wait for further feedback, since there are other really important things I will have to look into first - like making it freemium.

Have a great week!

Chris

very cool!