Make sure if you have enabled cross-origin ?

Also, to know exact error, you need to check console logs:
https://websitetoapk.com/docs/debugging-with-chrome.html

Alias password and keystore password is same in case you need not enter it. It is optional to use a different password, so it takes by default the password put the in command for both.

Make sure you have purchased genuine copy with us, only then it will work. If yes, kindly let us know registered email.

At the moment. Apps created are targeting API Level 31 which is compatible to Google Play. We will soon update to API Level 33 as well.

You need to get premium version which will allow you to change package name, and hence allow you to keep multiple apps installed at the same time.

Yes, rest assured. Our apps are fully compatible with new policy that came into effect on 01-Aug-2022. You will be able to publish the AAB file as they follow all the latest guidelines.

We are on API Level 31 so you can simply avoid this warning.

Bug has been already fixed after someone reported it on a support ticket. It should now work properly on newly build AABs.

Bug has been already fixed. It should now work properly.

It is currently not possible to put your own link and image in the banner.