We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running into an issue here where the following error is being thrown:
Uncaught TypeError: get(...) is not a function at Class.<anonymous> (stripe-element.js:23)
Looks like get(this, "stripev3.elements") is returning undefined, so calling that function is blowing up. Any idea why this might be happening?
get(this, "stripev3.elements")
The text was updated successfully, but these errors were encountered:
@adambedford Are you lazy loading the stripe elements?
Sorry, something went wrong.
We are seeing the same issue randomishly too. We are currently able to reproduce the issue on Ember 3.1.x and 3.8.x
We discovered a 'fix' that we do not quite understand why it works ... it could, perhaps just be luck.
Previously we loaded StripeV3 in a controller model(...) hook using an Ember.RSVP.hash(...)
model(...)
Ember.RSVP.hash(...)
model() { return hash({ someModel: asyncCall(), stripeLoader: this.get('stripe').load(), }); },
We changed this to:
beforeModel() { return this.get('stripe').load(); }, model() { return hash({ someModel: asyncCall(), }); },
And it appears to have 'fixed' the issue or at least reduced the frequency of failure.
NOTE: that the stripe service in our context is just a light wrapper around the 'stripev3' exported by the addon.
stripe
I wonder if it is b/c by the time you call get(this, "stripev3.elements"), the service hasn't been put into the container?
No branches or pull requests
Running into an issue here where the following error is being thrown:
Looks like
get(this, "stripev3.elements")
is returning undefined, so calling that function is blowing up. Any idea why this might be happening?The text was updated successfully, but these errors were encountered: