Hi Everybody,
I’m having a Stripe Plugin issue in trying to subscribe users to plan which previous canceled a plan. It hangs up and does nothing. I had assumed that Subscribing a user to a plan would work, after their previous plan was cancel.
Is this a bug?
Is there a different workflow I should be using or any settings on Stripe that need adjustments?
Is there some way I can detect when the Subscribe the User to a plan plug-in fails?
Any help or advice greatly appreciated.
-Chaz
Hopefully bubble did the right thing and expose for subsequent steps by using the result of previous step in dynamic expression whether or not the API call had an error. If not, you can always check the logs in Stripe dashboard to see what is going on.
I didn’t realize the previous step thing in the dynamic expressions had a feature for passing along errors. Very interesting.
They do not by default, only certain ones do, which are predominately API call actions. When directly connecting to Stripe via the API in the API connector, or setting up any API call in the API connector we have a checkbox for return errors, which when checked exposes a value from previous step (usually the API call) to see if an error was returned.
I suggest it here as plugins for Stripe are just simply pre-configured API calls for the most part, which is what Bubble has done likely for running the actions from the plugin, and if they did it correctly, they would have exposed the errors if an error exists when the action is run.
There are also triggers for when an ‘unhandled error occurs’ and also for ‘when an element has an error executing a workflow’.
It’s a shame that Result of step x does not support Error codes being passed along. The most I can do with the Bubble Stripe plug-in is deal with flow control if the returned subscription id is empty (in event of failure to create new sub).
“Do not show success message” is a kind of novelty feature of the action. I actually can’t show any javascript alert() in the application, since this designed to work with WebOS TV (LGTV) and that’s a no no, with the 5 way spatial navigation stuff as is. But that’s another story of how alert() appears on WebOS simulators and don’t even appear on the actual TV’s. They are running with their own special builds of Chrome.
I love the concept of having a checkbox for returning errors. Is this something you purely developed purely for in-house use or are you a Plug-In dev for Bubble as well?
My main issue besides not being to fully comprehend right away what was causing the plug-in action in the workflow in the first place. Was that when I did sort it all out. It is disturbing.
A New Subscription, should be a new Subscription and not tried to any previous Subscriptions.
This app I’m working on is going up on Smart TV’s and such. People come and go from these services. They will join for awhile, cancel, then come back a few months later or whenever and resubscribe.
While I can’t view their plug-in code, it appears they must be running a Query for any previously Cancel Subscriptions under the plan (the API ID, aka price_API_ID). If they find any, it refuses to create a whole new Subscription record. LOL.
We can manually add a new subscription to for the customer on Stripe and I updated the webhooks to deal with subscription added event. I then update the Stripe Subscription data for the customer in the whole backend workflow.
This is a bit of a PITA, since it requires human manual intervention and is not an easy automated system (which it should be).
I totally see how much these plugin Actions are merely pre-configure API calls. I wish I could simply fork Bubbles Stripe plug-in, and go dumpster diving into the related workflow action and update it myself.
It’s not on my mission plan to build a whole new Stripe Plug-in system from the ground up here. Plus, I’m relatively new to Bubble and still getting use to it. I’ve been doing a heck of a lot more custom Javascript coding work than I originally thought I would be into as is. I see where we can do forks on some of the plug-in’s to GitHub.
-Chaz
This is a feature Bubble put onto the API connector plugin when we setup API calls
To add the API connector plugin built by bubble go to plugins tab in app, go to add plugins and search api connector and install
It is possible to make everything automated, I do it for my apps and all my client apps.
No, as I just do my own API calls in the API connector to get the integration I need for the apps specific use case.
Bubble support email or bug reports
I build apps and some plugins for clients and for the Bubble marketplace as well as for my own uses.
You don’t need to…can just setup the API calls in the API connector
I don’t know javascript and I’ve been building full time on Bubble for over 6 years and I’ve used custom javascript a few times. You really shouldn’t need to use it in this case at all, and in most situations you shouldn’t need javascript, although there are definitely times that it can help achieve a function native bubble can not.
This topic was automatically closed after 70 days. New replies are no longer allowed.
