When using unsavedChangesAlerts(), DeleteAction and ForceDeleteAction present a second pop-up after a confirmation modal is accepted. about filament

[RalphMRivera]

@danharrin and @zepfietje - I've updated the reproduction repository connected to this issue to Filament 3.2.15 - The issue remains. Video attached. I am not sure if this comment suffices or if I should open a new issue.

issues-11042.mov

[danharrin]

Can you make sure your view cache is clear please? I definitely tested this

[RalphMRivera]

Hi @danharrin,

I went nuclear and ran the following on the reproduction repository:

composer update;
php artisan filament:upgrade;
npm update;
npm run build;
php artisan clear-compiled;
php artisan cache:clear;
php artisan config:cache;
php artisan debugbar:clear;
php artisan event:clear;
php artisan horizon:clear;
php artisan optimize:clear;
php artisan queue:clear;
php artisan route:clear;
php artisan view:clear;

I updated and pushed the reproduction repository.

I then nuked the browser cache and cookies. I did this on the reproduction repository and my current project (a separate Laravle app) and ended up with the same result. Additional note: I disabled all plug ins in Chrome to ensure there was no weird conflict.

Screen.Recording.2024-01-27.at.1.05.00.PM.mov

[danharrin]

Should be resolved by a308d57