Skip to content
New issue

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

Unable to send acceptance reminders #15874

Open
2 tasks done
filipc opened this issue Nov 22, 2024 · 3 comments
Open
2 tasks done

Unable to send acceptance reminders #15874

filipc opened this issue Nov 22, 2024 · 3 comments
Assignees
Labels
❓ not sure if bug This issue has not been confirmed as a bug yet

Comments

@filipc
Copy link

filipc commented Nov 22, 2024

Debug mode

Describe the bug

When calling snipeit:acceptance-reminder command email notifications are not being send

 ErrorException

  Attempt to read property "assignedTo" on null

  at app/Notifications/UnacceptedAssetReminderNotification.php:24
     20▕      */
     21public function __construct($checkout_info, $count)
     22▕     {
     23$this->count = $count;
  ➜  24$this->target = $checkout_info['acceptance']->assignedTo;
     25$this->acceptance = $checkout_info['acceptance'];
     2627▕     }
     28

Reproduction steps

run php artisan snipeit:acceptance-reminder -vvvv

Expected behavior

The emails should be sent.

Screenshots

No response

Snipe-IT Version

7.0.14

Operating System

Docker

Web Server

Nginx

PHP Version

8.1.2

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

Copy link

welcome bot commented Nov 22, 2024

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@snipe snipe added the ❓ not sure if bug This issue has not been confirmed as a bug yet label Dec 2, 2024
@snipe
Copy link
Owner

snipe commented Dec 2, 2024

I feel like this may have been fixed already. You might want to upgrade to the latest version.

@filipc
Copy link
Author

filipc commented Dec 4, 2024

@snipe it is not fixed. I am testing it on 7.1.15 and it is giving me the same error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
❓ not sure if bug This issue has not been confirmed as a bug yet
Projects
None yet
Development

No branches or pull requests

3 participants