Open
Description
[READ] Step 1: Are you in the right place?
Yes, this issue is specifically for the "Trigger Email from Firestore" extension.
[REQUIRED] Step 2: Describe your configuration
- Extension name: firestore-send-email
- Extension version: (Latest Version, 0.1.35)
- Configuration values:
- SMTP Settings: Verified and working
- Firestore Collection: Configured correctly
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
After updating to the latest version of the "Trigger Email from Firestore" extension, emails are no longer being triggered, and there are no error logs. The issue is reproducible.
- Install the latest version of the extension.
- Add a new Firestore document to trigger an email.
- Observe that the email is not sent and no errors appear in logs.
Expected result
- Email should be sent when a Firestore document is added.
Actual result
- No email is triggered.
- No error logs appear in Firebase logs.
Screenshots
- **Latest version of the extension:0.1.35
![Image](https://private-user-images.githubusercontent.com/179998409/411418061-70e6c85d-43b5-4a0b-8e32-f68332c9906e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNTcxMjAsIm5iZiI6MTczOTM1NjgyMCwicGF0aCI6Ii8xNzk5OTg0MDkvNDExNDE4MDYxLTcwZTZjODVkLTQzYjUtNGEwYi04ZTMyLWY2ODMzMmM5OTA2ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMlQxMDQwMjBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lNTBjZmZkMzAzNjhhZTljMDg2ZWYwMzc0ODJiOGQ3ZmQ2MDM4MzZhYTE0Y2Q1MDM0ZGRjNDAwYmFhM2QwZDhiJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.69YyVBRhufP9owhxHC3uFEZKm83lj8M1YvJW_KCWla0)
- **Old version of the extension (working):0.1.34
![Image](https://private-user-images.githubusercontent.com/179998409/411418351-aef25060-5ad3-4030-bc8c-0e677e6c7b1f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNTcxMjAsIm5iZiI6MTczOTM1NjgyMCwicGF0aCI6Ii8xNzk5OTg0MDkvNDExNDE4MzUxLWFlZjI1MDYwLTVhZDMtNDAzMC1iYzhjLTBlNjc3ZTZjN2IxZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMlQxMDQwMjBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kZjRjOTJiMjE0ZTE4ZDBlOWRiMjNlYzBhN2VhZWI0NDBjODI2ZjYwMGFhZWQxZTgzYWY5OWNjZGM3ZDkxNDcwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.g3yz-TSRP3haHySPKB6dF72q9Q0OLTdXtpsmD_gkMF4)
Recommended Next Steps
Since this extension is developed by a different team, I recommend checking the extension's GitHub repository to see if others have reported similar issues. Please confirm if this is a bug with the latest release and provide guidance on resolving it.
Let me know if more information is needed.
Thanks,
Vamshi