From my end, I realized that the new updated inApp Billing Extension is causing conflict kindly help me with others who probably will face the same problem.
Taking a look at my blocks I have followed with care the example blocks you provided in the aia
as workaround meanwhile you can use the previous version 3 of the extension and add the missing application metadata element manually into the manifest
Taifun
PS: I removed your example aia file… please never publish an aia file including a paid extension publicly… see also my terms and conditions…
It has nothing to do with Taifun’s extension;
1- It is necessary to experiment until the apk is created.
2- The page needs to stay open while the apk is being created.
Sorry @Taifun I didn’t share the aia I just typed the url https://subscribe.aia so it was not a real link take a look at it again or you can try to track Kodular activity log
For sure I don’t know how to add the manifest Library
I have tried to follow the steps but I don’t know where to get those libraries please Taifun if you don’t mind and if you have time please help me to add it can I send you the apk?
just use version 3 of the extension meanwhile and ignore the warning while uploading to Google Play… that version will work absolutely fine…
only after Nov 1st you will need version 3a to be able to upload a new version…
I want to take this opportunity to appreciate and my first thanks will be to @Taifun and the second precious person whom I have followed his guides until I have managed to solve all the problems is @bodymindpower
I used this method
Then when I got some error with signing key I used this method to fix all things up