-
Notifications
You must be signed in to change notification settings - Fork 64
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
Not able to log back in as Sample User #128
Comments
Yeah, right now "log in" means for paid customers only, not trial users. It should be fixed for sure but it's not a very high priority right now. |
@Glench is there a workaround for this? How can I login when I started a trial, but reinstalled the extension? |
@Glench I also ran into this issue during development. It seems like the user record should exist since |
a possible workaround would be to alert the user to use a different email. |
As @dm1014 mentioned it's not a very user-friendly way to do this and it becomes more complicated during the development when I have to test the trail flow locally. Every time I have to test the flow I would have to use a new email. |
This is a completely separate issue. You might consider creating a new discussion for it where you discuss in detail the issue you're getting. Also, if you use your developer email for trials in development mode you won't have to use different emails every time. |
I have a few people testing extensions for me. After I make changes and they install a revision of the extension they have to use a new email. That process is not practical or sustainable. I would propose that you provide an API call that would allow the removal of trial emails. That would allow the use of something like Postman to do a simple 'reset' of testing emails. It would be even better if this was offered through the UI, but I could get by with an API call for now. |
This has been fixed! See #108 |
It seems the system gets in a deadlock if a trial user reinstalls the app. Can you look into it?
The text was updated successfully, but these errors were encountered: