[PAID] 💲 In-App Billing : Advance Billing Extension (8.0.0)

Extensions
106

Please text me personally to get the latest version 7.1.1.

107

:loudspeaker: SDK is updated to latest v8.0.0 (Latest)

108

Hi @JEWEL , I purchased your extension last week. When I try to purchase, it says it successfully connected to the billing service, but it fails on Query Purchases with an unknown error. My app has only one yearly subscription available. Is there any way to get more detail on what the unknown error may be? I'm using MIT App Inventor, and the app compiles and I'm able to upload it for internal testing. Thanks.

109

Please upload your relevant blocks and the output screenshot.

110

Hope this works. Doesn't seem to be a good way to get the blocks out of App Inventor.

Blocks
Blocks1152×819 202 KB

Screenshot_20251028-073818.SteffesCAMSystem
Screenshot_20251028-073818.SteffesCAMSystem720×1612 42.7 KB

111

Right Click on some white pace in the Blocks Editor and select Download Blocks as Image

Right click on any block to download that block as an image, this will create a draggable image you can drag into a project blocks editor.

112

Is what I posted enough to know what the issue is, or do you need more information? I'm assuming that the Unknown Error is coming from Google. Any way to get more information on what that could be? Thanks.

113

Assuming you have setup the connection method during startup on the screen, other than that the other blocks seem to be fine. Right now, I am not sure why you are getting the unknown error issue, I will investigate soon and update you.

114

Sorry, yes start connection is in another block so I forgot to add it to the blocks I uploaded. Thanks for looking into this.

115

If it helps, I did publish a production version which is now live in the play store. I had one of my users update their production version and it works fine in production, but the internal test version still gives me the unknown error.

1 Like
116

Your blocks are fine. It appears there was an unexpected issue with the internal testing, and no resolution is required from the extension code. You may proceed with production using this current setup.

117

It looks like this is still an issue in production. If a user has a subscription, they can update to the new version and everything continues to work. If it's a new installation, they get the unknown error and cannot sign up for a new subscription.