lynndylanhurley / lynndylanhurley/devise_token_auth
confirmation email not sending with devise async IF concerns are loaded
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3.6k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
I'm using the latest version of this gem and I have the weirdest error !
I am trying to get the emails to be sent by active jobs with devise async.
Installed all the gems, and configured my User model as follows:
class User < ApplicationRecord
...
# Include default devise modules.
devise :database_authenticatable,
:recoverable, :rememberable, :trackable, :validatable,
:confirmable, :lockable, :async
include DeviseTokenAuth::Concerns::User
...
end
Reset Token email works just fine, BUT confirm email just never get sent.
If I remove the concern:
include DeviseTokenAuth::Concerns::User
Then the email is generated just fine but ... well the whole user model does'nt work and the confirm action is broken.
I'm at a loss here as the concern normally registers a notification to devise ? Soooo why is only this one email not working ?
Thanks a lot
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the User model configuration shown in the issue, then compare confirmation and reset-token behavior with and without DeviseTokenAuth::Concerns::User. Done means confirmation email delivery works while the concern remains included and the confirmation action still functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100