An update on this since the last message is that we managed to have this temporarily fixed by changing the "&__tenant=" query parameter to "&tenant=" and adapting our frontend code to use this. Also worth mentioning that we have slightly modified flow than the abp one since our url is pointing to the frontend instead of backend so we're not sure if it's something we missed in the configuration or not. But then again, we've had this flow for a long time and it worked fine, only after updating it stopped working. Thanks.
Hello, thanks for the reply. Proxies and packages are updated. For more context, this undefined error only happens after the user tries to set the password following the email link. The error page which opens seems to be a default one as well and after clicking on the "Home" button the same if check doesn't error out anymore unless trying to set the password again from the email.
I have tried with your example and use case its work fine.
have you tried setting it as nullable as per the abp documentation itself
Can you explain in details and which document you can refer.
sorry, I should have been more clear in my initial repro steps: Steps to reproduce the issue:
See screenshot bellow, same one as the initial one, line 78, "<OrganizationStatus?>"
I'm not sure what exactly you mean by "which document you can refer", maybe the abp documentation itself if you click on the link.
Screenshot from the documentation below in which it's explained how to handle nullable Enums.
Thanks for the reply, have you tried setting it as nullable as per the abp documentation itself and similar with my example and use case?
