I really do not understand where to set the placeholder…
It looks like, it depends on the API key.
As soon as I enter your API key I have the same placeholder as in your demo page…
The plugin’s state provides an example of an email stored in the plugin.
In case you would like to show a different example, you can use a source for your app database, like “Email” data type, with an example of email stored.
Yes, the Air Native plugin supports such a feature. In order to enable it within your app, a rebuild request is required. For more details, please contact the Air Native team.
Our plugin only makes connections between platforms, so, it doesn’t influence the timing when a corresponding payment system is sending back subscription status. By related documentation of the platform, there are no time limits mentioned. Thus, we can’t guarantee or specify how fast the platform replies with subscription status.
The provided answer follows from the results of the Air Native practical application.
As our plugin works with the data provided by the Google Play platform, we can’t confirm/speak/guarantee something on their behalf. The only available source of information is the Google Play Developer API documentation link shared above, where the description is quite general.
Currently, available sources are Air Native plugin supporting documentation: https://docs.zeroqode.com/plugins/air-native-plugin and API documentation of the related platforms (Google Play and Apple Store).
If there will be any other questions about our products, please drop a message.
Thank you for letting us know, the developer team will check that on our side too.
@floripaolo please let us know if there will be any other questions about our products, that have not been covered by my colleagues in parallel threads, that I can help with.
I am still waiting for an answer from @Ecaterina regarding the workflow error during a payment, which lead to charging the user without any registration of this action by Bubble.
Hi @floripaolo, here is a reply to one of the earlier discussed questions.
We’ve encountered the same issue (no workable keys generated), created and sent a bug report and so far await a reply from apilayer.com support team. Regretfully, so far they didn’t provide details on possible cause.
Once any news in this regard will become available, I will let you know asap.