Open afsinak opened 5 years ago
Same problem here. Suddenly stopped working.
Try doing swal.fire() worked for me
Swal.fire worked for me too.. why was that error??
On Thu, 24 Jan 2019, 13:46 GIP2000, notifications@github.com wrote:
Try doing swal.fire() worked for me
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/t4t5/sweetalert/issues/889#issuecomment-457106105, or mute the thread https://github.com/notifications/unsubscribe-auth/Asb7gRJMDSzxCdcmCaDzWvCkUyiHLSheks5vGWvBgaJpZM4aOxl4 .
https://sweetalert2.github.io/ here is the wiki
Same problem here, it works with .fire but now i need to go and find everywhere i've used it and update it? why was it changed?
yes @Gokalex (i don't know why)
The API has been updated. "swal" is now an object which has a method "fire". https://sweetalert2.github.io/#usage
@afsinak, as @Blair2004 explained you now need to include .fire
because sweetalert2
has been updated. If you don't have any other questions, you should close the issue.
I have this problem and i fix it with Swal.fire
if you use @toverux/ngx-sweetalert2, install sweetalert2 7.15.1 and .show() works fine.
This was a context lost (this)
i try to call Swal.fire on ie11 it didn't work
Unable to get property 'constructor' of undefined or null reference
Another way for this problem is I tried to refresh the browser using Ctrl
+ F5
, not just default refresh page but clear all the cache and load all the css and JS again and sweetalert works just fine.
You might have kept 'S' capital use small 's'. Swal(-something--) => "Wrong" swal(-something-) => "Correct"
Why is this entire thread here on the sweetalert repo when this is concerning sweetalert2 which is a completely different repo o_0, mysterious is the lord's way.
i am getting this error on swal function call.