I’ve forwarded this request to our team and they will disable these permissions
As for request purchase status - we only return a response from the Store. We recommend that you increase the pause after the action.
As for the workflow shown above, they will run parallel to each other, so there is no problem.
Actually those 2 parameters would have to be set by the developer (you). I contacted them. But “auto” would only not show the address request if the user already had an address stored with Stripe. Therefore it is not possible to remove it.
Another issue I am having is with Apple Purchase. Several (4), but not all customers apparently click several times to start the process. For this customer for example the log shows that the app store has been requested to process 7 times.
This causes to send several emails and show several error messages (sendgrid).
The log also shows that the workflows do not process the actions in a coherent sequence but apparently clustered/random. Unfortunately there is no way to download the log in order to show you, But there you can 7 requests to the app store.
Below you can see that the subscription gets scheduled 7 times in the backend.
Here is another example:
Since there is no way to reproduce this I do not know what happens and how to handle such an issue.
Allow me to provide you with all the responses below:
Currently, we are using the “getAvailablePurchase” method, which returns all the purchases.
However, we can’t see the verification of the status step on your side. Thus, we would like to advise you to separate this workflow. Here is an example of the required steps:
Run check subscription is an active action;
Add a pause;
Trigger after a pause a custom event. Please create a custom event and in this event save data from the plugin state.
Here is also the screencast from our devices, so you can see that it works on our side: Loom | Free Screen & Video Recording Software
This issue could be only in case your responsive settings for exactly this screen resolution is incorrect. Please check your settings for the resolution, which would be the same as on your phone device.
In case you already checked it, please reach the Bubble Support Team, since this issue is not related to the Air Native wrapper or default template. All layout issues could be reproduced for the reason of the Editor’s changes.
Can you please let me know which Stripe Plugin you are using in your app? By default, we use the Bubble Stripe plugin in our templates.
So, in case you are willing to receive any additional parameter, you should add it by yourself.
Our team can’t improve the plugin, which was created not by our team. Thus, please let me know which plugin you are using ( you can just send me a screenshot).
The processing can take some time and unfortunately, there is no way to stop it. The only thing you can do is try to set a limit on the number of clicks or sending mails.
The necessity of this change is related to the fact that your Pop-Up and element, which is placed in this Pop-Up are not visible on the page load, thus, the plugin just avoids this step.
For this custom event, we also recommend you to use not the AirNative a PopUp up Purchase, but from the same element where the action is proceeded ( in your case, it is the Apple Login element).
Unfortunately, it is could not be separated. Please note that this action is server-side action. Is used for validation of purchase and acknowledgment of Android purchase. This action can be found in the “Payment” tab.
Our Native team did not see your request because you sent it to our support team email. Thus, you didn’t receive a response from them. Now, we forwarded your emails to them, but please make sure that in case of necessity, you should reach the Native Team.
Yes, the cancelation is required only one action ( both for iOS and Android OS). The only difference is the necessity of completing these fields for the Android OS:
Seems like the root cause of the mentioned issue - is your device does not recognize the item on the mobile devices (responsive settings).
We just checked the code and the element is not visible for the page: