SMTP issue - nothing in the console? How to debug further?

[shuther]

I setup .env with fake SMTP settings from mailtrap. If I try to sign-in using an email such as test@example.com, I am getting the error message:
Something went wrong while sending the email. Please try again later.
However, there is nothing in the console to investigate further.

Is there a parameter I could use to get more logs about the issue? That would help a lot.

[deepakprabhakara]

Please add logs to this function here to figure out what might be going on - https://github.com/boxyhq/saas-starter-kit/blob/main/lib/email/sendEmail.ts#L22. We'll push a change to include more details in the logs.

[niwsa]

@shuther You need to signup first before logging in via magic link.

[shuther]

While debugging the issue, I discovered another "problem"; maybe I am missing an env to get proper debug statements? I am using for now: npm run dev
When I signed up for another account, I received on the browser side an error message (expected because I was playing with the DB):
Invalid prisma.user.findUnique()invocation: The columnUser.password does not exist in the current database.
However, there is nothing on the server console. Is it expected? I am not sure how I should be informed of such issue in production?

[shuther]

If we go back to the SMTP issue above (I reverted the changes in the DB), the email is sent (no sure what changed), however I am still stuck in this process when I click on the link:
On Safari in the console I have:

• Fetch API cannot load http://localhost:4002/_next/static/webpack/8f4902f3bd43ad9d.webpack.hot-update.json due to access control checks.

On Chrome I have:

• the page is loading and I reached the page: http://localhost:4002/auth/login?error=token-not-found, that is giving me a logging screen with the message in red: Verification token not found

And I still have nothing in the server console; I just see a bunch of:

@opentelemetry/instrumentation-http http instrumentation incomingRequest
Recording is off, propagating context in a non-recording span
@opentelemetry/instrumentation-http http instrumentation incomingRequest
Recording is off, propagating context in a non-recording span
Recording is off, propagating context in a non-recording span
Recording is off, propagating context in a non-recording span
Recording is off, propagating context in a non-recording span
Recording is off, propagating context in a non-recording span
Recording is off, propagating context in a non-recording span
Recording is off, propagating context in a non-recording span
 GET /_next/data/development/en/auth/join.json 200 in 30ms
@opentelemetry/instrumentation-http http instrumentation incomingRequest
Recording is off, propagating context in a non-recording span
items to be sent [
  {
    resource: Resource {
      _attributes: [Object],
      asyncAttributesPending: false,
      _syncAttributes: [Object],
      _asyncAttributesPromise: undefined
    },
    scopeMetrics: []
  }
]
items to be sent [
  {
    resource: Resource {
      _attributes: [Object],
      asyncAttributesPending: false,
      _syncAttributes: [Object],
      _asyncAttributesPromise: undefined
    },
    scopeMetrics: []
  }
]

thank you for your help.